Admin Server Failure To Start With Error BEA-000362 Server failed

There are 1 nested errors:

weblogic.management.DeploymentException: java.io.IOException: Error from fcntl() for file locking, Resource temporarily unavailable, errno=11

Solution: 

Remove these *.lok file and then try to start

$DOMAIN_HOME/edit.lok

$DOMAIN_HOME/config/lifecycle-config.xml.lok

$DOMAIN_HOME/config/ovd/default/ovd.lok

$DOMAIN_HOME/servers/AdminServer/tmp/AdminServer.lok

$DOMAIN_HOME/servers/WLS_FORMS/tmp/WLS_FORMS.lok

$DOMAIN_HOME/servers/WLS_REPORTS/tmp/WLS_REPORTS.lok

$DOMAIN_HOME/tmp/<filename>.lok

find . -name "*.lok" -exec rm -f {} \;

$DOMAIN_HOME/servers/AdminServer/data/store/default/_WLS_ADMINSERVER000000.DAT

$DOMAIN_HOME/servers/AdminServer/data/store/diagnostics/WLS_DIAGNOSTICS000000.DAT

$DOMAIN_HOME/servers/WLS_FORMS/data/store/default/_WLS_WLS_FORMS000000.DAT

$DOMAIN_HOME/servers/WLS_FORMS/data/store/diagnostics/WLS_DIAGNOSTICS000000.DAT

$DOMAIN_HOME/servers/WLS_REPORTS/data/store/default/_WLS_WLS_REPORTS000000.DAT

$DOMAIN_HOME/servers/WLS_REPORTS/data/store/diagnostics/WLS_DIAGNOSTICS000000.DAT

find . -name "*.DAT" -exec rename '.DAT' '.DAT_OLD' {} \;

Rolling Upgrade Error in Script

Few months back we were upgrading our AIX based database from 11gR2 [11.2.0.4] to 12c [12.2.0.1] by rolling upgrade. When we run physru_v3.sh script it is giving error:

WARN: The last execution of this script either exited in error or at the

-e user's request. At this point, there are three available options:

-e 1) resume the rolling upgrade where the last execution left off

-e 2) restart the script from scratch

-e 3) exit the script

-e

Option (2) assumes the user has restored the primary and physical

-e standby back to the original configuration as required by this script.

-e Enter your selection (1/2/3):

-e Sep 24 11:17:59 2019 [0-1] not a valid option - ''

-e Enter your selection (1/2/3):

-e Sep 24 11:17:59 2019 [0-1] not a valid option - ''

-e Enter your selection (1/2/3):

-e Sep 24 11:17:59 2019 [0-1] not a valid option - ''

Solution:

The issue is caused by the following setup:

in physru_v3.sh script change first line from below and then rerun the script

#!/bin/sh

to

#!/bin/bash  <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

Reports Server Component Status in REPORTS 12C

How to check report server component status as we previously check by opmnctl?

Due to decommissioning of opmn from 12c, that option is not available. There are two ways to check, unfortunately none of them as simple as opmn:

1. Run the command $DOMAIN_HOME/reports/bin/rwdiag.sh -findall 

If the reports server appears in the output, then it is up and running. If it does not appear, it is down

or

2. Check the REPORT Server components logs.

AVDF Console and Listener Port Change

Is it possible to change Audit Vault and Database Firewall listener and https console ports?

Answer:

It is not supported to change the AVDF database default listener port, it is also not supported to register the AV repository to a listener other than the one started by the AV installation. Doing either of these things it might "break" AVDF functionality.

The same is applicable for the default console https port change to 443.

For the moment there is no such possibility for AVDF hopefully feature will be available next release which is 19.1.

ORA-28041: Authentication protocol internal error

Expired user accounts can't change password and connect from 11.1.0.7 client to 12.2.0.1 DB+April2018PSU, failing with error 

ORA-28041: Authentication protocol internal error.

There is no issue with open user accounts connecting from 11.1.0.7 client to 12.2.0.1 DB+April2018PSU.

Also the expired user account connections from 11.1.0.7 client to 12.2.0.1DB+Jan2018PSU works fine. The issue started only after applying April 2018 PSU patch on DB server.

From Forms 11.1.2.2 and the SQLPLUS 11.1.0.7 that comes with Forms 11.1.2.2, expired user connections fail with below message:

ERROR:

ORA-28041: Authentication protocol internal error

In 12.2.0.1 databases, 11.1 client support has been removed. The following table shows which client and which database version are supported.

Cluster verification failed with PRVG-4574

Grid Infrastructure Upgrade from 12c to 19c

Error:

"Verifying Verify that the ASM instance was configured using an existing ASM parameter file. ...FAILED (PRVG-4574)"

Solution:

Copy ASM password file from local directory to ASM disk group.

1. Check the Path of ASM Password File

srvctl config asm -a

 

ASM home: <CRS home>

Password file: /oracle/product/12.2.0/grid/dbs/orapw+ASM         

Backup of Password file:

ASM listener: LISTENER

ASM is enabled.

ASM is individually enabled on nodes:

ASM is individually disabled on nodes:

ASM instance count: ALL

Cluster ASM listener: ASMNET1LSNR_ASM

 

2. Move ASM Passowrd File to ASM Disk Group

 

 When tried to move ASM password file from local directory to ASM disk group faced this error:

 

ASMCMD> pwcopy /oracle/product/12.2.0/grid/dbs/orapw+ASM +OCR_DG/orapwASM

ASMCMD> pwcopy /oracle/product/12.2.0/grid/dbs/orapw+ASM +OCR_DG/orapwASM

OPW-00010: Could not create the password file.

ORA-15056: additional error message

ORA-15221: ASM operation requires compatible.asm of 12.1.0.0.0 or higher

ORA-06512: at line 4

ASMCMD-9454: could not create new password file

 

error is visible now that our ASM compatible parameter is not set accordingly.

select group_number, name,compatibility from v$asm_diskgroup;

 
GROUP_NUMBER NAME                           COMPATIBILITY      
------------ ------------------------------ ----------------  
  1 		 OCR_DG                         11.2.0.2.0 

 

Change compatibility: 

alter diskgroup OCR_DG SET ATTRIBUTE 'compatible.asm' = '12.1';

ASMCMD> pwcopy /oracle/product/12.2.0/grid/dbs/orapw+ASM +OCR_DG/orapwASM

  

srvctl modify asm -pwfile +OCR_DG/orapwASM

 srvctl config asm -a

ASM home: <CRS home>

Password file: +OCR_DG/orapwASM    

Backup of Password file:

ASM listener: LISTENER

ASM is enabled.

ASM is individually enabled on nodes:

ASM is individually disabled on nodes:

ASM instance count: ALL

Cluster ASM listener: ASMNET1LSNR_ASM

 

Now rerun runcluvfy.sh and it will be passed.

ORA-19571: archived log RECID '***' STAMP '***' not found in control file

It seems that the Controlfile records are over-written.

1. check control_file_record_keep_time

show parameter control

NAME TYPE VALUE
———————————— ———– ——————————
control_file_record_keep_time integer 7

The value is very low. So please increase.

alter system set control_file_record_keep_time=20 scope=both;

System altered.

SQL> show parameter control

NAME TYPE VALUE
———————————— ———– ——————————
control_file_record_keep_time integer 20


2) Next you need to catalog the archivelogs to make the backup run without errors

RMAN> catalog start with '/u01/archive';

3. Now start the backup