One stop Oracle Database Knowledge center for DBAs

Friday, February 9, 2024

ORA-04063: package body "SYS.DBMS_RCVMAN" has errors

ISSUE DESCRIPTION

rman target /

Recovery Manager: Release 12.2.0.1.0 - Production on Fri Feb 9 19:26:23 2024

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

ORACLE error from target database:
ORA-04063: package body "SYS.DBMS_RCVMAN" has errors
ORA-06508: PL/SQL: could not find program unit being called: "SYS.DBMS_RCVMAN"

error executing package DBMS_RCVMAN in TARGET database
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00554: initialization of internal recovery manager package failed
RMAN-06429: TARGET database is not compatible with this version of RMAN

COMPILE the objects

rman target /

Recovery Manager: Release 12.2.0.1.0 - Production on Fri Feb 9 19:26:23 2024

STATUS of the OBJECTS

select owner,object_name,object_type,status from dba_objects where status='INVALID'
OWNER OBJECT_NAME OBJECT_TYPE STATUS
-------------------- ------------------------------ ----------------------- -------
SYS DBMS_RCVMAN PACKAGE BODY INVALID

SOLUTION

SQL> alter PACKAGE SYS.DBMS_RCVMAN compile BODY;

Warning: Package Body altered with compilation errors.

SQL>
SQL>
SQL>
SQL> sho error
Errors for PACKAGE BODY SYS.DBMS_RCVMAN:

LINE/COL ERROR
-------- -----------------------------------------------------------------
462/1    PL/SQL: Item ignored
463/8    PLS-00400: different number of columns between cursor SELECT
         statement and return value

8247/1   PL/SQL: Item ignored
8248/8   PLS-00400: different number of columns between cursor SELECT
         statement and return value

SQL>

SQL> @?/rdbms/admin/prvtrmns.plb

Session altered.

Package body created.

Session altered.

SQL>

SQL> !

rman target /

Recovery Manager: Release 12.2.0.1.0 - Production on Fri Feb 9 21:07:36 2024

connected to target database: DBNAME (DBID=123456789)

RMAN> exit

Recovery Manager complete.

Thursday, November 9, 2023

GATHER STATS for TABLE/SCHEMA/DATABASE/SYSTEM and LOCK STATS scripts

GATHER STATS for TABLE/SCHEMA/DATABASE/SYSTEM and LOCK STATS scripts

TABLE STATS

~~~~~~~~~~~~~~~~~~~~~~~~~~~~

EXEC DBMS_STATS.gather_table_stats('HR','EMPLOYEES');

EXEC DBMS_STATS.gather_table_stats('HR','EMPLOYEES',cascade=>TRUE);

EXEC DBMS_STATS.gather_table_stats('SCOTT', 'EMPLOYEES', estimate_percent => 15, cascade => TRUE);

exec dbms_stats.gather_table_stats(ownname=>'&Schema_name',tabname=>'&Table_name',estimate_percent=>DBMS_STATS.AUTO_SAMPLE_SIZE,cascade=>TRUE,degree =>4);

exec DBMS_STATS.GATHER_TABLE_STATS (ownname => '&OWNER' , tabname => '&TAB_NAME',cascade => true, estimate_percent => 10,method_opt=>'for all indexed columns size 1',granularity => 'ALL', degree => 1);

INDEX STATS

~~~~~~~~~~~~~~~~~~~~~~~~~~~~

EXEC DBMS_STATS.gather_index_stats('HR','EMPLOYEES_PK');

exec DBMS_STATS.GATHER_INDEX_STATS(ownname => '&OWNER',indname =>'&INDEX_NAME',estimate_percent =>DBMS_STATS.AUTO_SAMPLE_SIZE);

SCHEMA STATS

~~~~~~~~~~~~~~~~~~~~~~~~~~~~

EXEC DBMS_STATS.gather_schema_stats('SCOTT');

EXEC DBMS_STATS.gather_schema_stats('SCOTT', estimate_percent => 15, cascade => TRUE);

exec dbms_stats.gather_schema_stats(ownname=>'&schema_name',ESTIMATE_PERCENT=>dbms_stats.auto_sample_size,degree =>4);

exec dbms_stats.gather_schema_stats(ownname=>'&schema_name', CASCADE=>TRUE,ESTIMATE_PERCENT=>dbms_stats.auto_sample_size,degree =>4);

DATABASE STATS

~~~~~~~~~~~~~~~~~~~~~~~~~~~~

EXEC DBMS_STATS.gather_database_stats;

EXEC DBMS_STATS.gather_database_stats(estimate_percent => 15, cascade => TRUE);

exec dbms_stats.gather_database_stats(cascade=>TRUE,method_opt =>'FOR ALL COLUMNS SIZE AUTO');

EXEC DBMS_STATS.GATHER_DATABASE_STATS(ESTIMATE_PERCENT=>DBMS_STATS.AUTO_SAMPLE_SIZE,degree=>6);

EXEC DBMS_STATS.GATHER_DATABASE_STATS(ESTIMATE_PERCENT=>dbms_stats.auto_sample_size,CASCADE => TRUE,degree => 4);

DICTIONARY STATS

~~~~~~~~~~~~~~~~~~~~~~~~~~~~

EXEC DBMS_STATS.gather_dictionary_stats;

EXEC DBMS_STATS.gather_system_stats;

EXEC DBMS_STATS.gather_fixed_objects_stats;

lock/unlock statistics on table

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

exec dbms_stats.lock_table_stats('&OWNER', '&TAB_NAME');

exec dbms_stats.unlock_table_stats('&OWNER', '&TAB_NAME');

SELECT stattype_locked FROM dba_tab_statistics WHERE table_name='RAJ' and owner='SH';

CHECK STALE STATS

~~~~~~~~~~~~~~~~~~~~~~~~~~~~

SELECT owner, table_name, last_analyzed, stale_stats

FROM dba_tab_statistics

WHERE table_name='EMPLOYEES'

and owner='HR';

SELECT owner, table_name, index_name last_analyzed, stale_stats FROM dba_ind_statistics

WHERE table_name='EMPLOYEES'

and owner = 'HR';

Linux Script to Gather Stats

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

#!/bin/bash

. /home/oracle/.bash_profile

export ORACLE_HOME=/u01/app/oracle/product/19.3/db_home

export ORACLE_BASE=/u01/app/oracle

export ORACLE_SID=orcl

export DATE=$(date +%y-%m-%d_%H%M%S)

#### Gather HR schema stats ####

sqlplus / as sysdba << EOF > /tmp/HR_stats_gather_$DATE.log

EXEC DBMS_STATS.gather_schema_stats('HR');

EOF

echo "Stats gathered succeeded"

Tuesday, November 7, 2023

to CHECK & Pause/Resume/Kill a Running RMAN Backup

TO VIEW BACKUP STATUS for RMAN BACKUP Processes

SELECT b.opname,b.SID, b.SERIAL#, a.status,b.CONTEXT, b.SOFAR, b.TOTALWORK,

ROUND (b.SOFAR/b.TOTALWORK*100, 2) "% COMPLETE"

FROM gV$SESSION_LONGOPS b, gv$session a

WHERE b.OPNAME LIKE 'RMAN%'

AND b.OPNAME NOT LIKE '%aggregate%'

and a.sid=b.sid

AND b.TOTALWORK! = 0 AND b.SOFAR <> b.TOTALWORK;

TO GENERATE KILL SESSION scripts for RMAN BACKUP Processes

select 'alter system kill session '''||sid||'',''||serial#||''' immediate;' FROM V$SESSION_LONGOPS

WHERE OPNAME LIKE 'RMAN%' AND OPNAME NOT LIKE '%aggregate%'

AND TOTALWORK! = 0 AND SOFAR <> TOTALWORK;

1. Pause/Resume/Kill a Running RMAN Backup

To Check if there is an RMAN backup is currently running:

col START_TIME for a15

col END_TIME for a15

col TIME_TAKEN_DISPLAY for a10

col INPUT_BYTES_DISPLAY heading "DATA SIZE" for a10

col OUTPUT_BYTES_DISPLAY heading "Backup Size" for a11

col OUTPUT_BYTES_PER_SEC_DISPLAY heading "Speed/s" for a10

col output_device_type heading "Device_TYPE" for a11

SELECT to_char (start_time,'DD-MON-YY HH24:MI') START_TIME,to_char(end_time,'DD-MON-YY HH24:MI') END_TIME, time_taken_display, status,input_type, output_device_type,input_bytes_display, output_bytes_display,output_bytes_per_sec_display,COMPRESSION_RATIO COMPRESS_RATIO FROM v$rman_backup_job_details WHERE status like 'RUNNING%';

2. To Pause an already running RMAN backup: [This is only applicable for Linux OS]

set pages 0 feedback off

select 'TO PAUSE THE RUNNING RMAN BACKUP RUN THIS OS COMMAND:=> kill -STOP '||listagg (p.spid, ' ') WITHIN GROUP (ORDER BY p.spid) from v$session s, v$process p where s.program like 'rman@%' and p.addr=s.paddr;

3. To Resume an already "Paused" RMAN backup: [This is only applicable for Linux OS]

set pages 0 feedback off

select 'TO RESUME A "PAUSED" RMAN BACKUP RUN THIS OS COMMAND:=> kill -CONT '||listagg (p.spid, ' ') WITHIN GROUP (ORDER BY p.spid) from v$session s, v$process p where s.program like 'rman@%' and p.addr=s.paddr;

4. To Terminate an already running RMAN backup: [This is only applicable for Linux OS]

set pages 0 feedback off

select 'TO KILL THE RUNNING RMAN BACKUP RUN THIS OS COMMAND:=> kill -9 '||listagg (p.spid, ' ') WITHIN GROUP (ORDER BY p.spid) from v$session s, v$process p where s.program like 'rman@%' and p.addr=s.paddr;

Friday, February 10, 2023

Java (1.6) could not be located. OPatch cannot proceed!

We get below java error, when we try to query opatch utility like lsinventory, version, apply, rollback ...etc

follow below steps/workaround for the issue

Java (1.6) could not be located

Details of error are as follows.

[SERVER1]/u01/app$ OPatch/opatch version
Java (1.6) could not be located. OPatch cannot proceed!
OPatch returns with error code = 1
[SERVER1]/u01/app$ 
[SERVER1]/u01/app/OPatch $

OPatch cannot proceed!

This errors are related with the Opatch version or opatch utility was downloaded for a wrong platform or using older version of opatch.

Install the latest opatch

Use the JDK option like following.

which java

copy the java path and go to jdk location inside java home

opatch apply -jdk <<FULL_PATH_OF_JDK>

example output as below.

Use the JDK option like following.


[SERVER1]/u01/app$ 
[SERVER1]/u01/app$ OPatch/opatch version
Java (1.6) could not be located. OPatch cannot proceed!
OPatch returns with error code = 1
[SERVER1]/u01/app$ 
[SERVER1]/u01/app/OPatch $ 


[SERVER1]/u01/app/OPatch $ ./opatch lsinventory -jdk /export2/jdk/ -oh /u01/app/
Oracle Interim Patch Installer version 13.9.4.2.4
Copyright (c) 2021, Oracle Corporation. All rights reserved.


Oracle Home : /u01/app
Central Inventory : /u01/app/18c/oraInventory
from : /u01/app//oraInst.loc

OPatch version    : 12.2.0.1.33
OUI version       : 12.2.0.1.4

Log file location : /u01/app/cfgtoollogs/opatch/opatch2021-06-21_14-11-18PM_1.log

Lsinventory Output file location : /u01/app/cfgtoollogs/opatch/lsinv/lsinventory2021-06-21_14-11-18PM.txt

--------------------------------------------------------------------------------
ARU platform id: 226
ARU platform description:: Linux x86-64

Installed Top-level Products (1):

Oracle Database 12c                                                  12.2.0.1.0
There are 1 products installed in this Oracle Home.


There are no Interim patches installed in this Oracle Home.


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

OPatch succeeded.
[SERVER1]/u01/app/OPatch $

Thursday, December 22, 2022

Create file system in LINUX system which is Larger than 2TB

Create file system in LINUX system which is Larger than 2TB

###########################################################################
###########################################################################
Run the following command to install the e2fsprogs and parted :

yum install -y parted
yum install -y e2fsprogs

Perform the following operations to partition and format a data disk larger than 2 TiB in size and mount the file system.

Check whether a data disk exists.

Run the following command:
fdisk -l

A command output similar to the following one is returned. The command output includes information about the data disk. If no data disk information is returned, the instance does not have data disks attached.

Disk /dev/vdb: 3221.2 GB, 3221225472000 bytes, 6291456000 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Use the Parted tool to partition the data disk.

Run the following command to start partitioning:
parted /dev/sdb

Run the following command to convert the partition format from MBR to GPT:
mklabel gpt

Run the following command to create a primary partition and specify the start and end sectors for the partition:
mkpart primary 1 100%

where the 100% is total size of the disk allocated, you can choose as required.

Run the following command to check whether the partition is aligned:
align-check optimal 1

A command output similar to the following one is returned:
1 aligned

Note: -

If 1 not aligned is returned, the partition is not aligned.

We recommend that you run the following commands

and use the (<optimal_io_size> + <alignment_offset>)/<physical_block_size> formula to obtain the start sector number to align the partition for optimal performance.

For example, if the start sector number is 1024, you can then run the mkpart primary 1024s 100% command to create another primary partition.

cat /sys/block/vdb/queue/optimal_io_size
cat /sys/block/vdb/queue/minimum_io_size
cat /sys/block/vdb/alignment_offset
cat /sys/block/vdb/queue/physical_block_size

Run the following command to view the partition table:
print

Run the following command to exit the Parted tool:
quit

The following figure shows the result of partitioning by using the Parted tool.Partitioning by using Parted

Run the following command to enable the system to re-read the partition table:
partprobe

Run one of the following commands to create a file system for the /dev/vdb1 partition.
Run one of the following commands to create a file system based on your needs:

Create an ext4 file system.
mkfs -t ext4 /dev/vdb1

Run the following command to create a mount point named /test:
mkdir /test

Run the following command to mount the /dev/vdb1 partition to /test:
mount /dev/vdb1 /test

Run the following command to view the current disk space and usage:
df -h

If the command output shows the information of the new file system, the mount operation is successful. You can use the new file system.df output

(Recommended) Write the information of the new partition to /etc/fstab to enable this partition to be automatically mounted on system startup.

Run the cp /etc/fstab /etc/fstab.bak command to back up etc/fstab:

Run the following command to write information of the new partition to /etc/fstab:
echo `blkid /dev/vdb1 | awk '{print $2}' | sed 's/\"//g'` /test ext4 defaults 0 0 >> /etc/fstab

Note
You must run the command as the root user. If you are a common user,
you can run the su - command to switch to the root user, and then run this command.

Alternatively, you can run the sudo vi /etc/fstab command to edit /etc/fstab.
We recommend that you use a universally unique identifier (UUID) to reference the new partition in /etc/fstab.
You can run the blkid command to obtain the UUID of the new partition.

Run the following command to check the information of /etc/fstab:
cat /etc/fstab

###########################################################################

###########################################################################