SUN ORACLEWORLD: January 2017

Wednesday, 25 January 2017

PRVF-4007 User equivalence check failed for user grid

PRVF-4007 User equivalence check failed for user grid

This error occurs during RAC pre checks for crsinst. This is optional step for RAC installation which shows any pending pre checks to make your job simpler during installation.

This pre check is very helpful in prior to 11gR2 release as in 11gR2 release and next release you can make ssh configuration during clusterware installation. So simply you can ignore this error.

[grid@MYRACNODE1 grid]$ ./runcluvfy.sh stage -pre crsinst -n MYRACNODE1. local,MYRACNODE2.local -verbose

Performing pre-checks for cluster services setup

Checking node reachability...

Check: Node reachability from node "MYRACNODE1"

Destination Node Reachable?

------------------------------------ ------------------------

MYRACNODE1 yes

MYRACNODE2 yes

Result: Node reachability check passed from node "MYRACNODE1"

Checking user equivalence...

Check: User equivalence for user "grid"

Node Name Status

------------------------------------ ------------------------

MYRACNODE2 failed

MYRACNODE1 failed

Result: PRVF-4007 : User equivalence check failed for user "grid"

ERROR:

User equivalence unavailable on all the specified nodes

Verification cannot proceed

Pre-check for cluster services setup was unsuccessful on all the nodes.

[grid@MYRACNODE1 grid]$

This error occurred because you have not setup passwordless ssh configuration for grid user.

Solution:-

1) Ignore this error and proceed with your installation and make ssh configuration during the installation.Below are the screen shot for your reference.

2)

2) You can make manual ssh configuration by using below method.

cd /...grid/sshsetup

./sshUserSetup.sh -user oracle -hosts "myracnode1 myracnode2" –noPromptPassphrase

Tuesday, 17 January 2017

expdp failed with ORA-31641: unable to create dump file ORA-27054: NFS file system where the file is created or resides is not mounted with correct options

expdp failed with ORA-31641: unable to create dump file ORA-27054: NFS file system where the file is created or resides is not mounted with correct options

While performing expdp on database getting below error. This is known error and workaround is available to fix it.

DataPump export fails with below errors:
Export: Release 11.2.0.1.0 - Production on Sun Nov 25 21:00:36 2016
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.

Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
With the Partitioning, Real Application Clusters, Automatic Storage Management, OLAP,
Data Mining and Real Application Testing options
ORA-39001: invalid argument value
ORA-39000: bad dump file specification
ORA-31641: unable to create dump file "/devotd_dpump/expdp_metadata_vspp_sun.dmp"
ORA-27054: NFS file system where the file is created or resides is not mounted with correct options
Additional information: 3
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3

This is the common error DBA faces. Reason for getting this error may be bug or incorrect option while mounting the NFS mount point. Also this known bug.

Solution
The solution which worked in this case was to set the below event which disables the mount point parameter checking:
sqlplus / as sysdba
alter system set events '10298 trace name context forever, level 32';

Or:

Set the following event in the init.ora
event="10298 trace name context forever, level 32"

Or
setting event is workaround provided by oracle if this not help you then kindly mount the NFS mount point with correct option as below-
# mount -F nfs -o rw,bg,hard,rsize=32768,wsize=32768,vers=3,forcedirectio,nointr,proto=tcp,suid host:/folder1/to1 /folder2/to2

Reference - ORA-27054: NFS file system where the file is created or resides is not mounted with correct options (Doc ID 781349.1)

Thursday, 5 January 2017

RMAN-06172: no AUTOBACKUP found or specified handle is not a valid copy or piece

RMAN-06172 is known error we faced while restoring control file through RMAN. During controlfile restoration you should provide controlfile backup piece with complete path.

Below is the example given for your ref.

1. RMAN Backup details on source :

RMAN> backup current controlfile format '/RMAN_TEST/control_%U';

Starting backup at 05-JAN-17
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=38 device type=DISK
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
including current control file in backup set
channel ORA_DISK_1: starting piece 1 at 05-JAN-17
channel ORA_DISK_1: finished piece 1 at 05-JAN-17
piece handle=/RMAN_TEST/control_0frp8ndk_1_1 tag=TAG20170105T112955 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:03
Finished backup at 05-JAN-17

Starting Control File and SPFILE Autobackup at 05-JAN-17
piece handle=/u01/app/oracle/recovery_area/CDB1/autobackup/2017_01_05/o1_mf_s_932470203_d6wckw0y_.bkp comment=NONE
Finished Control File and SPFILE Autobackup at 05-JAN-17

RMAN>

2. Restoration on target

[oracle@Server RMAN_TEST]$

[oracle@Server RMAN_TEST]$ sqlplus "/ as sysdba"

SQL*Plus: Release 12.1.0.1.0 Production on Thu Jan 5 11:31:31 2017

Connected to an idle instance.

SQL> startup nomount pfile='/RMAN_TEST/initMYTEST.ora';

ORACLE instance started.

Total System Global Area 217157632 bytes

Fixed Size 2286656 bytes

Variable Size 159386560 bytes

Database Buffers 50331648 bytes

Redo Buffers 5152768 bytes

SQL>

SQL> exit

Disconnected from Oracle Database 12c Enterprise Edition Release 12.1.0.1.0 - 64bit Production

With the Partitioning, OLAP, Advanced Analytics and Real Application Testing options

[oracle@Server RMAN_TEST]$

[oracle@Server RMAN_TEST]$ cd /

[oracle@Server /]$

[oracle@Server /]$ rman target /

Recovery Manager: Release 12.1.0.1.0 - Production on Thu Jan 5 11:32:13 2017

connected to target database: MYTEST (not mounted)

RMAN> restore controlfile from 'control_0frp8ndk_1_1';

Starting restore at 05-JAN-17

using target database control file instead of recovery catalog

allocated channel: ORA_DISK_1

channel ORA_DISK_1: SID=20 device type=DISK

RMAN-00571: ===========================================================

RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============

RMAN-00571: ===========================================================

RMAN-03002: failure of restore command at 01/05/2017 11:33:04

RMAN-06172: no AUTOBACKUP found or specified handle is not a valid copy or piece

RMAN>

RMAN> restore controlfile from '/RMAN_TEST/control_0frp8ndk_1_1';

Starting restore at 05-JAN-17

using channel ORA_DISK_1

channel ORA_DISK_1: restoring control file

channel ORA_DISK_1: restore complete, elapsed time: 00:00:01

output file name=/RMAN_TEST/control_01.ctl

Finished restore at 05-JAN-17

RMAN>

Now you can mount the database and carry forward your restoration task.

Thank you!

RMAN full backup on Standby (RAC) and Restoration on new server as primary (Standalone)

RMAN full backup on Standby (RAC) and Restoration on new server as primary (Standalone)

Requirement – Take RMAN full consistent backup on standby RAC database and then restore this consistent RMAN full backup on to the test server and open the restored database in READ WRITE mode.

Scenario and consideration –

1) Migration from one server to another

2) RAC to single instance

3) ASM to file system

4) Standby to Primary

Task involved in this activity-

Stop recovery on standby database.
Take RMAN full backup on standby database.
Start recovery on standby database.
Transfer backup piece to the target server.
Restore rman backup and open database in READ WRITE mode.
Perform post restoration activities.

We have NOT made any changes to production and standby side. We have performed restoration on test server.

1 Stop recovery on standby database.

SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;

Crosscheck MRP process is not running on standby database and then proceed with next step.

2 RMAN full backup on standby RAC database.

Take rman full backup on standby database. Below are the script details which were used to take the RMAN full backup on standby database.

$ nohup sh rman_l0_bkp.sh &

$ cat rman_l0_bkp.sh

export ORACLE_SID=mystd1

export ORACLE_HOME=/oracle/app/oracle/product/11.2.0/dbhome_1;

/oracle/app/oracle/product/11.2.0/dbhome_1/bin/rman target / CMDFILE=/backup/rman_bkp/RMAN_BKP_TEST/rman_l0_bkp.rcv log=/backup/rman_bkp/RMAN_BKP_TEST/rman_l0_bkp.log

$cat rman_l0_bkp.rcv

run{

allocate channel c1 type disk format '/backup/rman_bkp/RMAN_BKP_TEST/FULL_mystd_%U';

allocate channel c2 type disk format '/backup/rman_bkp/RMAN_BKP_TEST/FULL_mystd_%U';

allocate channel c3 type disk format '/backup/rman_bkp/RMAN_BKP_TEST/FULL_mystd_%U';

allocate channel c4 type disk format '/backup/rman_bkp/RMAN_BKP_TEST/FULL_mystd_%U';

allocate channel c5 type disk format '/backup/rman_bkp/RMAN_BKP_TEST/FULL_mystd_%U';

allocate channel c6 type disk format '/backup/rman_bkp/RMAN_BKP_TEST/FULL_mystd_%U';

allocate channel c7 type disk format '/backup/rman_bkp/RMAN_BKP_TEST/FULL_mystd_%U';

allocate channel c8 type disk format '/backup/rman_bkp/RMAN_BKP_TEST/FULL_mystd_%U';

backup AS COMPRESSED BACKUPSET full database tag bkp_level_0 format '/backup/rman_bkp/RMAN_BKP_TEST/FULL_mystd_%U' database;

backup controlfile format '/backup/rman_bkp/RMAN_BKP_TEST/control_mystd_%U';

release channel c1;

release channel c2;

release channel c3;

release channel c4;

release channel c5;

release channel c6;

release channel c7;

release channel c8;

}

Start the recovery process on standby database after successful completion of RMAN full backup.

# Background redo apply. Control is returned to the session once the apply process is started.

ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION;

3. Transfer this RMAN full backup to target server .

Use ftp or scp to transfer the backup to target server. Crosscheck the backup piece and it’s size on source and target server.

4. Restoration of RMAN backup on target server .

Create a PFILE for the single instance database using the production/standby RAC parameter file.

a. please modify the following parameters depending on the directory structure of the new host: audit_file_dest, background_dump_dest, control_files, core_dump_dest, log_archive_dest_1, user_dump_dest etc

b. remove RAC specific parameters such as cluster_database_instances, cluster_database etc

c. for the parameter undo_tablespace, mention any one undo tablespace name

Starting from 10g it is NOT mandatory to copy the RMAN backup pieces to exactly the same location on the new host as the production location.

Below is sample init.ora file used for this activity. Please make the modification according to your application requirements.

*._optim_peek_user_binds=FALSE

*.audit_file_dest='/oracle/app/oracle/admin/myprod/adump'

*.audit_sys_operations=FALSE

*.audit_trail='NONE'

*.cluster_database=false

*.compatible='11.2.0.0.0'

*.control_files='/database/data/myprod/controlfile/contol01.ctl','/database/data/myprod/controlfile/control02.ctl'

*.db_block_checking='TRUE'

*.db_block_checksum='TYPICAL'

*.db_block_size=8192

*.db_create_file_dest='/database/data/myprod/datafile'

*.db_domain=''

*.db_name='myprod'

*.diagnostic_dest='/oracle/app/oracle'

*.dispatchers='(PROTOCOL=TCP) (SERVICE=myprodXDB)'

*.dml_locks=800

*.job_queue_processes=10

*.log_archive_dest_1='location=/database/data/myprod/archive'

*.log_archive_format='%t_%s_%r.arc'

*.log_archive_max_processes=6

*.memory_target=0

*.nls_length_semantics='CHAR'

*.open_cursors=1000

*.optimizer_capture_sql_plan_baselines=FALSE

*.optimizer_features_enable='10.2.0.4'

*.optimizer_index_cost_adj=100

myprod.pga_aggregate_target=52428800

*.processes=350

*.query_rewrite_enabled='FALSE'

*.remote_login_passwordfile='EXCLUSIVE'

*.resource_limit=TRUE

*.sec_case_sensitive_logon=FALSE

*.session_cached_cursors=150

*.sessions=5280

*.sga_max_size=4g

#*.sga_max_target=4g

*.standby_file_management='AUTO'

*.undo_retention=7200

myprod.undo_tablespace='UNDOTBS1'

create spfile from initmyprod.ora

SQL> CREATE SPFILE FROM PFILE=’/path/initmyprod.ora’;

Use the spfile created above to STARTUP NOMOUNT the database on the new host

bash-2.05b$ sqlplus "/ as sysdba"

SQL*Plus: Release 11.2.0.4.0 Production on Tue Dec 27 09:53:45 2016

Connected to an idle instance.

SQL>

SQL> startup nomount;

ORACLE instance started.

Total System Global Area 4275781632 bytes

Fixed Size 2253216 bytes

Variable Size 4211084896 bytes

Database Buffers 50331648 bytes

Redo Buffers 12111872 bytes

SQL>

Now invoke RMAN and restore the controlfile specifying the location where the controlfile

piece is transferred on this new server. You can mount the database once the controlfile

is restored successfully.

RMAN> restore controlfile from '/database/RMAN/RMAN_BKP_TEST/control_mystd_msroess4_1_1’;

Starting restore at 27-DEC-16
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=156 devtype=DISK

channel ORA_DISK_1: restoring control file
channel ORA_DISK_1: restore complete, elapsed time: 00:00:02
output filename= /database/data/myprod/controlfile/contol01.ctl

output filename= /database/data/myprod/controlfile/control02.ctl

Finished restore at 27-DEC-16

RMAN>

RMAN> alter database mount;

database mounted
released channel: ORA_DISK_1

SQL> select name, open_mode,log_mode, database_role, controlfile_type from v$database;

NAME OPEN_MODE LOG_MODE DATABASE_ROLE CONTROL

--------- -------------------- ------------ ---------------- -------

MYPROD MOUNTED ARCHIVELOG PHYSICAL STANDBY STANDBY

You can skip this step if you have restored the RMAN backup pieces to exactly the

same location they were backed up on production. If this is not the case then you

need to catalog the RMAN backup pieces to make RMAN aware of thier new location

on the new host. Note that CATALOG BACKUPPIECE command is available only starting from

10g.

RMAN> catalog start with '/database/RMAN/RMAN_BKP_TEST';

searching for all files that match the pattern /database/RMAN/RMAN_BKP_TEST

List of Files Unknown to the Database

=====================================

File Name: /database/RMAN/RMAN_BKP_TEST/FULL_mystd_mlroeq5e_1_1

File Name: /database/RMAN/RMAN_BKP_TEST/FULL_mystd_mmroeq5e_1_1

File Name: /database/RMAN/RMAN_BKP_TEST/FULL_mystd_mnroeq5f_1_1

File Name: /database/RMAN/RMAN_BKP_TEST/FULL_mystd_moroeq5f_1_1

File Name: /database/RMAN/RMAN_BKP_TEST/FULL_mystd_mproeq5f_1_1

File Name: /database/RMAN/RMAN_BKP_TEST/FULL_mystd_mqroeq5g_1_1

File Name: /database/RMAN/RMAN_BKP_TEST/FULL_mystd_mrroeq5g_1_1

File Name: /database/RMAN/RMAN_BKP_TEST/control_mystd_msroess4_1_1

File Name: /database/RMAN/RMAN_BKP_TEST/nohup.out

File Name: /database/RMAN/RMAN_BKP_TEST/rman_l0_bkp.log

Do you really want to catalog the above files (enter YES or NO)? YES

cataloging files...

cataloging done

List of Cataloged Files

=======================