Syed Saad Ali

Oracle ACE Pro

Oracle Solution Architect

Oracle E-Business Suite

Oracle Cloud Infrastructure

Oracle Fusion Middleware

Oracle Database Administration

Oracle Weblogic Administration

Syed Saad Ali

Oracle ACE Pro

Oracle Solution Architect

Oracle E-Business Suite

Oracle Cloud Infrastructure

Oracle Fusion Middleware

Oracle Database Administration

Oracle Weblogic Administration

Oracle Database Material

May 17, 2017 ORA-01012: not logged on
Errors/Workarounds10gOracle Database Material

ERROR

sqlplus / as sysdba
SQL*Plus: Release 10.2.0.4.0 - Production on Tue Jun 24 12:32:12 2013
Copyright (c) 1982, 2007, Oracle.  All Rights Reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
Connected.
SQL> select status from v$instance;
select status from v$instance;
*
ERROR at line 1:
ORA-01012: not logged on

SOLUTION

“The ORA-01012: not logged on” error occurred due to heavy load in the database. If there is maximum number of sessions connected to the database, database does not allow sysdba privileged user as well as other users are connected to the database.

Solution 1: First Check /etc/hosts file if there is incorrect host name or IP correct it and try Start database.

Solution 2: Without shutdown anything just kill that database processes which are not local processes. Local means background processes.

ps -ef | grep $ORACLE_SID | grep -v grep | grep "LOCAL=NO" | awk '{print $2}' | xargs kill -9

Solution 3: Shut down application server sessions

Solution 4: Shut down database server then start database server and database.
May 16, 2017 could not validate asmsnmp password due to following errorora-01031:insufficent privileges
Errors/Workarounds11gOracle Database Material

ERROR

During Create new database, It shows following errors
“could not validate asmsnmp password due to following error ora-01031:insufficent privileges”

SOLUTION

Step 1. Create Password file for ASM Instance

$orapwd file=/u0/app/11.2.0/grid/dbs/orapw+ASM password=anypassword
Step 2.   $sqlplus / as sysasm
SQL>create user asmsnmp identified by password;
SQL>grant sysdba to asmsnmp;
May 15, 2017 Enterprise Manager DB Control/DB Console (OEM) is not working after Changing Hostname or IP Address
Errors/Workarounds10gErrors/Workarounds11gOracle Database Material

ERROR

Enterprise Manager DB Control/DB Console (OEM) is not working after Changing Hostname or IP Address

 

SOLUTION

Step 1. Set $ORACLE_HOSTNAME to the old hostname

  
export ORACLE_HOSTNAME=old_name

Step 2. De-configure the old DB Console by running the following command:

  
$ORACLE_HOME/bin/emca -deconfig dbcontrol db

Step 3. $ORACLE_HOSTNAME to the new hostname:

export ORACLE_HOSTNAME=new_name

Step 4. Configure the new DB Console

$ORACLE_HOME/bin/emca -config dbcontrol db -repos recreate
May 14, 2017 ORA-39700: database must be opened with upgrade option
Errors/Workarounds10gErrors/Workarounds11gOracle Database Material

ERROR

ORA-39700: database must be opened with upgrade option

SOLUTION

Step 1: Open with Upgrade Option

SQL> startup upgrade;

 

Step 2: upgrade database – it means run script $ORACLE_HOME/rdbms/admin/catupgrd.sql

SQL> @/u01/app/oracle/product/11.2.0/db_home1/rdbms/admin/catupgrd.sql;
Step 3: Shutdown database and Startup

SQL> shutdown immediate;

SQL> startup;

 

Step 4: Run script $ORACLE_HOME/rdbms/admin/utlrp.sql – for recompile all invalid PL/SQL packages

SQL> @/u01/app/oracle/product/11.2.0/db_home1/rdbms/admin/utlrp.sql