Thursday, January 19, 2017

RMAN-06023 and Specification does not match any backup

If you come across a situation that you want to use RMAN to restore but there is a backup without using RMAN.

When you try to restore using RMAN you will receive the error message as below
RMAN-06023: no backup or copy of datafile xx found to restore

When you query catalog you will get below message as no backups in repository.

RMAN> LIST BACKUP OF DATABASE;
Specification does not match any backup in the repository

If you want to use the backups taken using HOT backup mode or copy, you must register all data files, archive logs into RMAN catalog.

Use below command to register.
RMAN> catalog start with '/ora-backup/ORCL/arch-bkp/' noprompt;
RMAN> catalog start with '/ora-backup/ORCL/data-bkp/' noprompt;

If your archive logs and data files are in same location then you need to run only once.

Once all backup copies are registered in RAM you can follow below link to restore

Regards,
Satishbabu Gunukula, Oracle ACE


error in invoking target 'agent nmhs' of makefile

I come across a situation that servers & Operating systems are (O/S) are getting upgraded and we cannot perform in place upgrade for easy roll backing capability.

Also new O/S does not support the Database version.

We need to restore the Oracle database into unsupported Server version. We have copied the Database binaries and during the Database upgrade we got below error.

error in invoking target 'agent nmhs' of makefile

Workaround:
During upgrade or clone  you will get this error when relink is running

Here is the workaround 
ls $ORACLE_HOME/sysman/lib/ins_emagent.mk

Search for the line 
$(MK_EMAGENT_NMECTL)
Change it to:
$(MK_EMAGENT_NMECTL) -lnnz11

https://community.oracle.com/thread/1093616

Goto Database upgrade window and click on "Retry" and upgrade should run successfully.

Regards
Satishbabu Gunukula, Oracle ACE
http://www.oracleracexpert.com

SUSPEND and RELEASE background Jobs in SAP

To Suspend all Background jobs follow below steps. Normally uses will do this before upgrade or maintenance activity.

To SUSPEND
SE38 --> Program: BTCTRNS1 --> Run




To RELEASE 
SE38 --> Program: BTCTRNS2 --> Run


Thanks
Satishbabu Gunukula, Oracle ACE
http://www.oracleracexpert.com

OPatch failed with error code 73

If users copy the ORACLE_HOME from one system to another unix system, make sure you run the clone command. If not the ORACLE_HOME information will not be registered in the oraInventory.

Some times users may get below errors when they copy ORACLE_HOME, ORACLE Inventory from a different system. Note that the path and SID may not be same.

Inventory load failed... OPatch cannot load inventory for the given Oracle Home.
Possible causes are:
   Oracle Home dir. path does not exist in Central Inventory
   Oracle Home is a symbolic link
   Oracle Home inventory is corrupted
LsInventorySession failed: OracleHomeInventory gets null oracleHomeInfo


OPatch failed with error code 73

By running ORACLE_HOME "Clone" command will create new inventory (if missing) and also takes care of re-linking of libraries..etc

$ORACLE_HOME/oui/bin/runInstaller -clone ORACLE_HOME="/home/oracle/product/v11203" ORACLE_HOME_NAME="Ora11203_home1" ORACLE_BASE="/oracle" oracle.sysman.ccr:PRE_REQUISITE=true

Before you run above command make sure you have /etc/oraInst.loc file with inventory_loc and inst_group.

Note that there are many parameters available and full list of parameters visit
https://docs.oracle.com/cd/E35328_01/E35330/html/vmiug-manager-runinstaller.html

Thanks,
Satish

Enhance Tracing for SAP HANA SSO Issues

SAP HANA will not login and authentication failures and errors. To troubleshooting any login/authentication/sso issue user need to enable tracing

Normally I enable below tracing to get the required info

ALTER SYSTEM ALTER CONFIGURATION ('indexserver.ini', 'SYSTEM') set ('trace', 'authentication') = 'debug' with reconfigure;
ALTER SYSTEM ALTER CONFIGURATION ('indexserver.ini', 'SYSTEM') set ('trace', 'crypto') = 'debug' with reconfigure;
ALTER SYSTEM ALTER CONFIGURATION ('xsengine.ini', 'SYSTEM') set ('trace', 'authentication') = 'debug' with reconfigure;
ALTER SYSTEM ALTER CONFIGURATION ('xsengine.ini', 'SYSTEM') set ('trace', 'xssession') = 'debug' with reconfigure;
ALTER SYSTEM ALTER CONFIGURATION ('xsengine.ini', 'SYSTEM') set ('trace', 'xsauthentication') = 'debug' with reconfigure;

Reproduce the issue and collect the trace. After you collect all the necessary info you can run below command to disable the tracing.

ALTER SYSTEM ALTER CONFIGURATION ('indexserver.ini', 'SYSTEM') UNSET ('trace', 'authentication');
ALTER SYSTEM ALTER CONFIGURATION ('indexserver.ini', 'SYSTEM') UNSET ('trace', 'crypto');
ALTER SYSTEM ALTER CONFIGURATION ('xsengine.ini', 'SYSTEM') UNSET ('trace', 'authentication');
ALTER SYSTEM ALTER CONFIGURATION ('xsengine.ini', 'SYSTEM') UNSET ('trace', 'xssession');
ALTER SYSTEM ALTER CONFIGURATION ('xsengine.ini', 'SYSTEM') UNSET ('trace', 'xsauthentication');

Hope this helps,

Regards
Satishbabu Gunukula, Oracle ACE
http://oracleracexpert.com