1. SQLPLUS NOT FOUND:
[oracle@eprax01 ~]$ sqlplus '/ as sysdba'
-bash: sqlplus: command not found
Soln: ORACLE HOME and PATH is not set.
Do this:
[oracle@eprax01 ~]$ export PATH=/u01/app/oracle/product/11.2.0/bin:$PATH
[oracle@eprax01 ~]$ export ORACLE_HOME=/u01/app/oracle/product/11.2.0
[oracle@eprax01 ~]$ export ORACLE_SID=prd
[oracle@eprax01 ~]$ sqlplus '/ as sysdba'
SQL*Plus: Release 11.2.0.1.0 Production on Tue Jul 5 16:40:51 2011
Copyright (c) 1982, 2009, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
With the Partitioning, Automatic Storage Management, OLAP, Data Mining
and Real Application Testing options
SQL>
2. ORA-00845: MEMORY_TARGET not supported on this system
Soln:
Starting from Oracle 11g the automatic memory management feature is now defined with parameter MEMORY_TARGET and
MEMORY_MAX_TARGET.
If /dev/shm value is less than MEMORY_TARGET parameter.
Make sure /dev/shm is properly mounted. You can see it by,
df -h
# mount -t tmpfs shmfs -o size=13g /dev/shm
3. ORA-12528: TNS:listener: all appropriate instances are blocking new connections
This happens becausewhen you start the database in nomount/ mount state then for some reason this particular
service(Which is mounted/started) is blocked by Oracle.
Symptoms:
[oracle@eprax01 admin]$ sqlplus sys/XXXX@dev
SQL*Plus: Release 11.2.0.1.0 Production on Tue Jul 5 23:14:54 2011
Copyright (c) 1982, 2009, Oracle. All rights reserved.
ERROR:
ORA-12528: TNS:listener: all appropriate instances are blocking new connections
Soln:
Add the below entry in your TNSNAMES.ORA
( UR = A)
Ex:
DEV =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = eprax01)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = dev)
(UR = A)
)
)
Then try to connect again:
[oracle@eprax01 admin]$ sqlplus sys/XXXX@dev as sysdba
SQL*Plus: Release 11.2.0.1.0 Production on Tue Jul 5 23:24:35 2011
Copyright (c) 1982, 2009, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
With the Partitioning, Automatic Storage Management, OLAP, Data Mining
and Real Application Testing options
SQL>
5. RMAN-05001: auxiliary file name +DATA/prd/datafile/example.269.755015953 conflicts with a file used by the target database
Problem with init.ora parameters: db_file_name_convert and log_file_name_convert, make sure they have proper values.
For ex:
*.db_file_name_convert=('+DATA/prd','+DATA/dev')
*.log_file_name_convert=('+DATA/prd','+DATA/dev')
6. ORA-15041: diskgroup "DATA" space exhausted
Add disks to diskgroup.
7. RMAN-04006: error from auxiliary database: ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
[oracle@eprax01 ~]$ sqlplus '/ as sysdba'
-bash: sqlplus: command not found
Soln: ORACLE HOME and PATH is not set.
Do this:
[oracle@eprax01 ~]$ export PATH=/u01/app/oracle/product/11.2.0/bin:$PATH
[oracle@eprax01 ~]$ export ORACLE_HOME=/u01/app/oracle/product/11.2.0
[oracle@eprax01 ~]$ export ORACLE_SID=prd
[oracle@eprax01 ~]$ sqlplus '/ as sysdba'
SQL*Plus: Release 11.2.0.1.0 Production on Tue Jul 5 16:40:51 2011
Copyright (c) 1982, 2009, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
With the Partitioning, Automatic Storage Management, OLAP, Data Mining
and Real Application Testing options
SQL>
2. ORA-00845: MEMORY_TARGET not supported on this system
Soln:
Starting from Oracle 11g the automatic memory management feature is now defined with parameter MEMORY_TARGET and
MEMORY_MAX_TARGET.
If /dev/shm value is less than MEMORY_TARGET parameter.
Make sure /dev/shm is properly mounted. You can see it by,
df -h
# mount -t tmpfs shmfs -o size=13g /dev/shm
3. ORA-12528: TNS:listener: all appropriate instances are blocking new connections
This happens becausewhen you start the database in nomount/ mount state then for some reason this particular
service(Which is mounted/started) is blocked by Oracle.
Symptoms:
[oracle@eprax01 admin]$ sqlplus sys/XXXX@dev
SQL*Plus: Release 11.2.0.1.0 Production on Tue Jul 5 23:14:54 2011
Copyright (c) 1982, 2009, Oracle. All rights reserved.
ERROR:
ORA-12528: TNS:listener: all appropriate instances are blocking new connections
Soln:
Add the below entry in your TNSNAMES.ORA
( UR = A)
Ex:
DEV =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = eprax01)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = dev)
(UR = A)
)
)
Then try to connect again:
[oracle@eprax01 admin]$ sqlplus sys/XXXX@dev as sysdba
SQL*Plus: Release 11.2.0.1.0 Production on Tue Jul 5 23:24:35 2011
Copyright (c) 1982, 2009, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
With the Partitioning, Automatic Storage Management, OLAP, Data Mining
and Real Application Testing options
SQL>
5. RMAN-05001: auxiliary file name +DATA/prd/datafile/example.269.755015953 conflicts with a file used by the target database
Problem with init.ora parameters: db_file_name_convert and log_file_name_convert, make sure they have proper values.
For ex:
*.db_file_name_convert=('+DATA/prd','+DATA/dev')
*.log_file_name_convert=('+DATA/prd','+DATA/dev')
6. ORA-15041: diskgroup "DATA" space exhausted
Add disks to diskgroup.
7. RMAN-04006: error from auxiliary database: ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
You may encounter this issue while creating physical standby or clone your database using RMAN.
The reason is: When you clone your database using RMAN, the auxiliary instance is started(IN NOMOUNT STATE) for this reason the services with the listener is not registered because to pick up the new service name the database must be at least in mount state. In our case we put the database in nomount state and hence the abover error pops-out when you run: DUPLICATE TARGET DATABASE TO <>
Soln:
To avoid this, connect Auxiliary database locally and connect to Target database remotely using services.
Set Oracle SID as AUX database and then logon to RMAN as shown below:
[oracle@eprax01 ~]$ rman target sys/XXXXX@prd auxiliary /
8. ORA-04021: timeout occurred while waiting to lock object
Not advicible every time, This is issue with shared_pool as it's not able to get this new code registered.
alter system flush shared_pool
9. Message 1053 not found; No message file for product=network, facility=TNS
Set ORACLE_HOME properly to the installation directory
10. TNS-12543: TNS:destination host unreachable
Add the service entery in TNSNAMES.ORA
DR01 =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = dba.asteroid.com)(PORT = 1523))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = DR01)
)
)
12. RMAN-05538: WARNING: implicitly using DB_FILE_NAME_CONVERT
released channel: prm01
released channel: prm02
released channel: prm04
released channel: prm05
released channel: stb01
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 08/22/2011 05:53:58
RMAN-05501: aborting duplication of target database
RMAN-05001: auxiliary file name /u01/app/oracle/oradata/prim/example01.dbf conflicts with a file used by the target database
RMAN-05001: auxiliary file name /u01/app/oracle/oradata/prim/users01.dbf conflicts with a file used by the target database
RMAN-05001: auxiliary file name /u01/app/oracle/oradata/prim/undotbs01.dbf conflicts with a file used by the target database
RMAN-05001: auxiliary file name /u01/app/oracle/oradata/prim/sysaux01.dbf conflicts with a file used by the target database
The reason is: When you clone your database using RMAN, the auxiliary instance is started(IN NOMOUNT STATE) for this reason the services with the listener is not registered because to pick up the new service name the database must be at least in mount state. In our case we put the database in nomount state and hence the abover error pops-out when you run: DUPLICATE TARGET DATABASE TO <>
Soln:
To avoid this, connect Auxiliary database locally and connect to Target database remotely using services.
Set Oracle SID as AUX database and then logon to RMAN as shown below:
[oracle@eprax01 ~]$ rman target sys/XXXXX@prd auxiliary /
8. ORA-04021: timeout occurred while waiting to lock object
Not advicible every time, This is issue with shared_pool as it's not able to get this new code registered.
alter system flush shared_pool
9. Message 1053 not found; No message file for product=network, facility=TNS
Set ORACLE_HOME properly to the installation directory
10. TNS-12543: TNS:destination host unreachable
Network was down, the issue was with IP address. Set the ipaddress and the network parameters properly
11.RMAN-06217: not connected to auxiliary database with a net service name
Add the service entery in TNSNAMES.ORA
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = dba.asteroid.com)(PORT = 1523))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = DR01)
)
)
12. RMAN-05538: WARNING: implicitly using DB_FILE_NAME_CONVERT
released channel: prm01
released channel: prm02
released channel: prm03
released channel: prm04
released channel: prm05
released channel: stb01
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 08/22/2011 05:53:58
RMAN-05501: aborting duplication of target database
RMAN-05001: auxiliary file name /u01/app/oracle/oradata/prim/example01.dbf conflicts with a file used by the target database
RMAN-05001: auxiliary file name /u01/app/oracle/oradata/prim/users01.dbf conflicts with a file used by the target database
RMAN-05001: auxiliary file name /u01/app/oracle/oradata/prim/undotbs01.dbf conflicts with a file used by the target database
RMAN-05001: auxiliary file name /u01/app/oracle/oradata/prim/sysaux01.dbf conflicts with a file used by the target database
RMAN-05001: auxiliary file name /u01/app/oracle/oradata/prim/system01.dbf conflicts with a file used by the target database
Add db_file_name_convert=('/u01/app/oracle/oradata/prim','/u01/app/oracle/oradata/DR01') in Duplicate command and then add log_file_name_convert in init.ora of STANDBY database.
No comments:
Post a Comment