Upgrading the Recovery Catalog Schema OR Database

The catalog schema must support the highest target version it supports.  Therefore, when a target database is upgraded, you need to also upgrade the RMAN catalog schema.  Connect to RMAN from the target database (with highest version) and connect to the catalog schema to upgrade the schema version.  



Oracle Production DB Version  11.2.0.4
Oracle Catalog DB Version      10.2.0.4


Upgrade Catalog Schema

Production DB:


bash-4.1$ ./rman target / catalog rman/xxxxxxxx@catsserp


Recovery Manager: Release 11.2.0.4.0 - Production on Sat Jul 9 17:02:43 2016

Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.

connected to target database: SSAERP (DBID=3389811866)
connected to recovery catalog database
PL/SQL package RMAN.DBMS_RCVCAT version 10.02.00.04 in RCVCAT database is too old

RMAN> upgrade catalog;

recovery catalog owner is RMAN

enter UPGRADE CATALOG command again to confirm catalog upgrade



RMAN> upgrade catalog;

recovery catalog upgraded to version 11.02.00.04
DBMS_RCVMAN package upgraded to version 11.02.00.04
DBMS_RCVCAT package upgraded to version 11.02.00.04




Catalog DB

SQL> conn rman/xxxxxxx
Connected.


SQL> select * from rcver;

VERSION
------------
11.02.00.04



SQL> conn / as sysdba
Connected.


SQL> grant create type to rman;

Grant succeeded.

Relocate of Baan to Other Server

Restore Baan Folder ssaerp to new server


#/ssaerp/bse/lib/

#gedit tabledef6.2

Replace of Oracle old home to new home

Check the listener

Slowness of Baan 514 port Rexec

 Add Comments of name server 

/etc/resolv.conf

Enable the Port 7150 Baan Login

Can also use baanlogin protocol this is taken from solution 70306

SOLUTION DESCRIPTION:
1. Rexec versus BaanLogin method
============================

When using the BaanLogin method password information is send in a encrypted way.


Short description of The BaanLogin functionality:

The BaanLogin functionality provides:

* The BaanLogin protocol.
* A client-side interface for the BaanLogin protocol.
* A daemon that will act as a server for BaanLogin.
* A changed BaanLogicService on Windows/NT that supports the BaanLogin protocol.
* The possibility to select between the BaanLogin- and rexec-protocol based on additional information in configuration files.

To be able to accept BaanLogin-requests, the BaanLogin daemon must be started and running at the Baan server.
And, at the client side, BW has to be configured to use the BaanLogin method.

SERVER CONFIGURATION
Windows NT:

The daemon runs as a service and is implemented in the BaanLogicService.
To enable BaanLogin-request configure the BaanLogic Service as follows: 
> Start the Baan NT Manager on the Baan -NT server.
> Select the Logic service, and click on it with your right mouse button
> Select Protocol...
Now a window pops up having the following fields:

Listen
Protocol
O Rexec
O BaanLogin

Port ....
ONamed Pipe

To enable the BaanLogin protocol mark the checkbox in front of BaanLogin.

Selection of the correct Port number:
When enabling only Rexec protocol you have to choose Port 512.
This is because the Rexec protocol is hardcoded to port 512.
So, also when enabling both Rexec and BaanLogin protocol you have to use port 512.
When enabling only the BaanLogin protocol the default port is 7150. You can change this to another portnumber.

After stopping & starting the BaanLogic service the new settings will become active.

To disable BaanLogin request turn off the BaanLogin option again and restart the BaanLogic service.

UNIX:

Check the permission of Blogind6.2

#/ssaerp/bse/bin/blogind6.2

The BaanLogin functionality is implemented as a daemon process: blogind6.x

To enable BaanLogin-request do the following::

Usage: blogind6.1 [-vV] [-d] [-p Portnumber] [-kK]

> Log in as root at the Baan Unix server because you must have root permission to start the BaanLogin daemon.
> Take care the BSE environment variables are correctly set.
> Start the BaanLogin daemon process as follows:

blogind6.1 -p Portnumber

When you start blogind6.1 without specifying any options it will default take port 7150.
To run the blogind6.1 in a kind of debug mode specify the -d option, for example:

# blogind6.1 -d
# Daemon: listen for first connection.

Daemon: Incoming connection, spawn child.
Deamon: revert to listen-mode.
Child: handle BaanLogin request.
Child: received: user kvddool, action 1
bseEnv /c1/b40c/bse/bin/ipc_boot, bseVersion 6.1
Child: logon for kvddool OK.
Child: pwd status = -5, message = -2005: The aging for name is turned off.
Child: starting /c1/b40c/bse/bin/ipc_boot6.1.

Here you see someone logs on successfully using the BaanLogin method.

To stop the BaanLogin daemon execute the following command:
blogind6.1 -k



CLIENT CONFIGURATION
To configure the client to use the BaanLogin method follow these steps:

> Start BW Configuration 
> Select Method: BaanLogin
> The portnumber will be set to the default: 7150
The portnumber must be the same number as the one you configured the BaanLogic Service (Windows NT) for or you specified when starting the blogind.6.x (UNIX). 
> Save the configurarion and login Baan.

When the BaanLogin protocol is selected the following entries are written into the .bwc file:
protocol=BAAN
portnumber=7150

When the Rexec protocol is selected the following entries are written into the .bwc file:
protocol=EXEC
portnumber=512

ORA-02096: specified initialization parameter is not modifiable with this option

I getting below error while changing db_file_name_convert.

SQL> alter system set db_file_name_convert='/ora_dat/drssaerp','/ora_dat/ssaerp','/ora_idx/drssaerp','/ora_idx/ssaerp';

ORA-02096 "Specified initialization parameter is not modifiable with this option





Solution:


SQL> alter system set db_file_name_convert='/ora_dat/drssaerp','/ora_dat/ssaerp','/ora_idx/drssaerp','/ora_idx/ssaerp';

scope=spfile;

Altered System.

Restart the database once after that u can see the modified parameter.

SQL> show parameter log_file_name_convert

log_file_name_convert  string      /ora_dat/drssaerp/, /ora_dat/ssaerp

SQL> show parameter db_file_name_convert

db_file_name_convert   string      /ora_dat/drssaerp/, /ora_dat/ssaerp/,

                                                       /ora_idx/drssaerp/, /ora_idx/ssaerp/

To see the list of parameters which are session level or system level modifiable, you can query the V$PARAMETER view like below:

SQL> Select name,isses_modifiable,issys_modifiable from v$parameter;

ORA-02096 "Specified initialization parameter is not modifiable with this option

Cause: Though the initialization parameter is modifiable, it cannot be modified using the specified command.

Action: Check the DBA Guide for information about under what scope the parameter may be modified

Log Files in Oracle RAC

The Cluster Ready Services Daemon (crsd) Log Files

Log files for the CRSD process (crsd) can be found in the following directories:

ORA_CRS_HOME/log/hostname/crsd

the crsd.log file is archived every 10MB as crsd.101, crsd.102 ...
ORACLE_CRS_HOME/log//alert.log

Oracle Cluster Registry (OCR) Log Files

The Oracle Cluster Registry (OCR) records log information in the following location:

ORA_CRS_HOME/log/hostname/client

Cluster Synchronization Services (CSS) Log Files

You can find CSS information that the OCSSD generates in log files in the following locations:

ORA_CRS_HOME/log/hostname/cssd
OCSSD responsible for inter node health monitoring and instance endpoint recovery.

It runs as oracle user.  

The cssd.log file is archived every 20MB as cssd.101, cssd.102....

Event Manager (EVM) Log Files

Event Manager (EVM) information generated by evmd is recorded in log files in the following locations:

ORA_CRS_HOME/log/hostname/evmd

RACG Log Files

The Oracle RAC high availability trace files are located in the following two locations:

ORA_CRS_HOME/log/hostname/racg
$ORACLE_HOME/log/hostname/racg

Core files are in the sub-directories of the log directories. Each RACG executable has a sub-directory assigned exclusively for that executable. The name of the RACG executable sub-directory is the same as the name of the executable.

VIP Log Files

You can find VIP related log files under following location :
ORA_CRS_HOME/log/nodename/racg

OCR logs 
OCR logs (ocrdump, ocrconfig, ocrcheck) log files are stored in $ORA_CRS_HOME/log//client/ directory. 

SRVCTL logs

srvctl logs are stored in two locations, $ORA_CRS_HOME/log//client/ and in $ORACLE_HOME/log//client/ directories.

Slm Server not starting BaanERP in Cluster Server

Slm Server not starting in Second node of cluster server.

After I search found some error in license file. I plan to moved license file from first node to second after that it was working fine.

/usr/baan/shared/license

I requested new license from Baan Support.


#SlmServer -s

Log file path  /usr/baan/shared/log/log.SlmServer

2016-06-19[00:45:22]:E:root: Pid 18541 Uid 0 Euid 0 Gid 0 Egid 0
2016-06-19[00:45:22]:E:root: Errno 125 (Address already in use)
2016-06-19[00:45:22]:E:root: Log_mesg: TCP bind() to port 6005 failed, error 125
2016-06-19[00:45:22]:E:root:
2016-06-19[00:45:22]:E:root: ******* E N D of Error message *******
2016-06-19[00:45:24]:E:root:
2016-06-19[00:45:24]:E:root: ******* S T A R T of Error message *******
2016-06-19[00:45:24]:E:root: Log message called from /view/MaintSLM7_0.nlbaucc.ccadm.snapshot/vobs/tt/lib/nw_1/sock_server.c:
#221 keyword: ipc
2016-06-19[00:45:24]:E:root: Pid 18541 Uid 0 Euid 0 Gid 0 Egid 0
2016-06-19[00:45:24]:E:root: Errno 125 (Address already in use)
2016-06-19[00:45:24]:E:root: Log_mesg: TCP bind() to port 6005 failed, error 125
2016-06-19[00:45:24]:E:root:

CLSRSC-117: Failed to start Oracle Clusterware stack Oracle 12c clusterware

Install Grid software on RAC01 was sucessfully but Second RAC02 having a problem while running the root.sh script.


RAC02:


#/ora/grid/root.sh


[INS-35423]The installer has detected that Oracle Clusterware is not running on the local Node.

I am running the runinstaller as oracle user and it can see the cluster fine.

$ crsctl check crs
CRS-4638: Oracle High Availability Services is online
CRS-4537: Can not Cluster Ready Services is offline
CRS-4529: Cluster Synchronization Services is online
CRS-4533: Event Manager is offline

/ora/grid/log/rac02/agent/ohasd/oraagent_oracle/oraagent_oracle.log


status msg [CRS-5017: The resource action "ora.asm start" encountered the following error:
ORA-00443: background process "MMNL" did not start
. For details refer to "(:CLSN00107:)" in "/ora/grid/log/rac02/agent/ohasd/oraagent_oracle/oraagent_oracle.log".
] for start for resource: ora.asm 1 1
2016-06-06 23:03:49.377: [    AGFW][3043145488] {0:9:5} Agent sending reply for: RESOURCE_START[ora.asm 1 1] ID 4098:584
2016-06-06 23:03:49.449: [ora.asm][3045246736] {0:9:5} [start] (:CLSN00107:) clsn_agent::start }






Solution:


Rac installation  on Virtual Machine

I increased the memory of rac02 server.

[root@rac02 grid]# ./root.sh

Performing root user operation for Oracle 12c 

The following environment variables are set as:

    ORACLE_OWNER= oracle

    ORACLE_HOME=  /ora/grid

Enter the full pathname of the local bin directory: [/usr/local/bin]: 

The contents of "dbhome" have not changed. No need to overwrite.

The contents of "oraenv" have not changed. No need to overwrite.

The contents of "coraenv" have not changed. No need to overwrite.

Entries will be added to the /etc/oratab file as needed by

Database Configuration Assistant when a database is created

Finished running generic part of root script.

Now product-specific root actions will be performed.

Using configuration parameter file: /ora/grid/crs/install/crsconfig_params

2016/06/07 00:00:02 CLSRSC-363: User ignored prerequisites during installation

CRS-2791: Starting shutdown of Oracle High Availability Services-managed resources on 'rac02'

CRS-2673: Attempting to stop 'ora.crsd' on 'rac02'

CRS-2790: Starting shutdown of Cluster Ready Services-managed resources on 'rac02'

CRS-2673: Attempting to stop 'ora.asm' on 'rac02'

CRS-2673: Attempting to stop 'ora.LISTENER_SCAN1.lsnr' on 'rac02'

CRS-2677: Stop of 'ora.LISTENER_SCAN1.lsnr' on 'rac02' succeeded

CRS-2673: Attempting to stop 'ora.scan1.vip' on 'rac02'

CRS-2677: Stop of 'ora.asm' on 'rac02' succeeded

CRS-2677: Stop of 'ora.scan1.vip' on 'rac02' succeeded

CRS-2672: Attempting to start 'ora.scan1.vip' on 'rac01'

CRS-2676: Start of 'ora.scan1.vip' on 'rac01' succeeded

CRS-2672: Attempting to start 'ora.LISTENER_SCAN1.lsnr' on 'rac01'

CRS-2676: Start of 'ora.LISTENER_SCAN1.lsnr' on 'rac01' succeeded

CRS-2673: Attempting to stop 'ora.ons' on 'rac02'

CRS-2677: Stop of 'ora.ons' on 'rac02' succeeded

CRS-2673: Attempting to stop 'ora.net1.network' on 'rac02'

CRS-2677: Stop of 'ora.net1.network' on 'rac02' succeeded

CRS-2792: Shutdown of Cluster Ready Services-managed resources on 'rac02' has completed

CRS-2677: Stop of 'ora.crsd' on 'rac02' succeeded

CRS-2673: Attempting to stop 'ora.ctssd' on 'rac02'

CRS-2673: Attempting to stop 'ora.mdnsd' on 'rac02'

CRS-2673: Attempting to stop 'ora.gpnpd' on 'rac02'

CRS-2677: Stop of 'ora.gpnpd' on 'rac02' succeeded

CRS-2677: Stop of 'ora.mdnsd' on 'rac02' succeeded

CRS-2677: Stop of 'ora.ctssd' on 'rac02' succeeded

CRS-2673: Attempting to stop 'ora.evmd' on 'rac02'

CRS-2673: Attempting to stop 'ora.storage' on 'rac02'

CRS-2677: Stop of 'ora.storage' on 'rac02' succeeded

CRS-2673: Attempting to stop 'ora.asm' on 'rac02'

CRS-2677: Stop of 'ora.evmd' on 'rac02' succeeded

CRS-2677: Stop of 'ora.asm' on 'rac02' succeeded

CRS-2673: Attempting to stop 'ora.cluster_interconnect.haip' on 'rac02'

CRS-2677: Stop of 'ora.cluster_interconnect.haip' on 'rac02' succeeded

CRS-2673: Attempting to stop 'ora.cssd' on 'rac02'

CRS-2677: Stop of 'ora.cssd' on 'rac02' succeeded

CRS-2673: Attempting to stop 'ora.gipcd' on 'rac02'

CRS-2677: Stop of 'ora.gipcd' on 'rac02' succeeded

CRS-2793: Shutdown of Oracle High Availability Services-managed resources on 'rac02' has completed

CRS-4133: Oracle High Availability Services has been stopped.

CRS-4123: Starting Oracle High Availability Services-managed resources

CRS-2672: Attempting to start 'ora.mdnsd' on 'rac02'

CRS-2672: Attempting to start 'ora.evmd' on 'rac02'

CRS-2676: Start of 'ora.mdnsd' on 'rac02' succeeded

CRS-2676: Start of 'ora.evmd' on 'rac02' succeeded

CRS-2672: Attempting to start 'ora.gpnpd' on 'rac02'

CRS-2676: Start of 'ora.gpnpd' on 'rac02' succeeded

CRS-2672: Attempting to start 'ora.gipcd' on 'rac02'

CRS-2676: Start of 'ora.gipcd' on 'rac02' succeeded

CRS-2672: Attempting to start 'ora.cssdmonitor' on 'rac02'

CRS-2676: Start of 'ora.cssdmonitor' on 'rac02' succeeded

CRS-2672: Attempting to start 'ora.cssd' on 'rac02'

CRS-2672: Attempting to start 'ora.diskmon' on 'rac02'

CRS-2676: Start of 'ora.diskmon' on 'rac02' succeeded

CRS-2789: Cannot stop resource 'ora.diskmon' as it is not running on server 'rac02'

CRS-2676: Start of 'ora.cssd' on 'rac02' succeeded

CRS-2672: Attempting to start 'ora.cluster_interconnect.haip' on 'rac02'

CRS-2672: Attempting to start 'ora.ctssd' on 'rac02'

CRS-2676: Start of 'ora.ctssd' on 'rac02' succeeded

CRS-2676: Start of 'ora.cluster_interconnect.haip' on 'rac02' succeeded

CRS-2672: Attempting to start 'ora.asm' on 'rac02'

CRS-2676: Start of 'ora.asm' on 'rac02' succeeded

CRS-2672: Attempting to start 'ora.storage' on 'rac02'

CRS-2676: Start of 'ora.storage' on 'rac02' succeeded

CRS-2672: Attempting to start 'ora.crsd' on 'rac02'

CRS-2676: Start of 'ora.crsd' on 'rac02' succeeded

CRS-6017: Processing resource auto-start for servers: rac02

CRS-2673: Attempting to stop 'ora.LISTENER_SCAN1.lsnr' on 'rac01'

CRS-2672: Attempting to start 'ora.ons' on 'rac02'

CRS-2677: Stop of 'ora.LISTENER_SCAN1.lsnr' on 'rac01' succeeded

CRS-2673: Attempting to stop 'ora.scan1.vip' on 'rac01'

CRS-2677: Stop of 'ora.scan1.vip' on 'rac01' succeeded

CRS-2672: Attempting to start 'ora.scan1.vip' on 'rac02'

CRS-2676: Start of 'ora.scan1.vip' on 'rac02' succeeded

CRS-2672: Attempting to start 'ora.LISTENER_SCAN1.lsnr' on 'rac02'

CRS-2676: Start of 'ora.ons' on 'rac02' succeeded

CRS-2676: Start of 'ora.LISTENER_SCAN1.lsnr' on 'rac02' succeeded

CRS-6016: Resource auto-start has completed for server rac02

CRS-6024: Completed start of Oracle Cluster Ready Services-managed resources

CRS-4123: Oracle High Availability Services has been started.

2016/06/07 00:04:38 CLSRSC-343: Successfully started Oracle clusterware stack

2016/06/07 00:05:22 CLSRSC-325: Configure Oracle Grid Infrastructure for a Cluster ... succeeded

[root@rac02 grid]#