DBA_REGISTRY_HISTORY IS SHOWING 11.2.0.20 FOR THE COMMENT COLUMN FOR 11.2.0.3

DBA_REGISTRY_HISTORY IS SHOWING 11.2.0.20  FOR THE COMMENT COLUMN FOR 11.2.0.3

After upgrading from 11.2.0.2se to 11.2.0.3se, DBA_REGISTRY_HISTORY shows Patchset 11.2.0.2.0 for 11.2.0.3. For example:

select * from dba_registry_history order by action_time;

ACTION_TIME	ACTION	NAMESPACE	VERSION	ID	BUNDLE_SERIES	COMMENTS
2007-04-27 1:24:06.000000 PM	CPU	SERVER	10.2.0.2.0	5689957		CPUJan2007
2009-05-23 2:38:48.000000 AM	UPGRADE	SERVER	10.2.0.4.0			Upgraded from 10.2.0.2.0
2011-11-10 12:31:30.905842 PM	VIEW INVALIDATE			8289601		view invalidation
2011-11-10 12:31:31.708360 PM	UPGRADE	SERVER	11.2.0.3.0			Upgraded from 10.2.0.4.0
2011-11-10 12:59:23.315431 PM	APPLY	SERVER	11.2.0.3	0	PSU	Patchset 11.2.0.2.0

Oracle has confirmed that it is a bug (Bug 13360611).

DBA_REGISTRY_HISTORY provides information about upgrades, downgrades, and critical patch updates that have been performed on the database.

Column	Datatype	NULL	Description
ACTION_TIME	TIMESTAMP(6)		The time the upgrade, downgrade, or patch action was completed
ACTION	VARCHAR2(30)		The specific action (for example, UPGRADE or DOWNGRADE)
NAMESPACE	VARCHAR2(30)		The namespace of the components affected (for example, SERVER)
VERSION	VARCHAR2(30)		The version number of the server (for example, 10.2.0.1.0)
ID	NUMBER		The identification number of the Critical Patch Update
COMMENTS	VARCHAR2(255)		Additional comments about the action taken

Oracle Database Limits in Oracle 11g Release 2 (11.2, 11gR2)

Oracle Database Limits in Oracle 11g Release 2  (11.2, 11gR2)

This article lists the limits of values associated with Oracle database functions and objects on several levels. There is usually a hard-coded limit that cannot be exceeded. This value may be further restricted for any given operating system.

Database limits are divided into four categories:

·         Datatype Limits

Datatypes	Limit	Comments
BFILE	Maximum size: 4 GB Maximum size of a file name: 255 characters Maximum size of a directory name: 30 characters Maximum number of open BFILEs: see Comments	The maximum number of BFILEs is limited by the value of theSESSION_MAX_OPEN_FILES initialization parameter, which is itself limited by the maximum number of open files the operating system will allow.
BLOB	Maximum size: (4 GB - 1) * DB_BLOCK_SIZEinitialization parameter (8 TB to 128 TB)	The number of LOB columns per table is limited only by the maximum number of columns per table (that is, 1000).
CHAR	Maximum size: 2000 bytes	None
CHAR VARYING	Maximum size: 4000 bytes	None
CLOB	Maximum size: (4 GB - 1) * DB_BLOCK_SIZEinitialization parameter (8 TB to 128 TB)	The number of LOB columns per table is limited only by the maximum number of columns per table (that is, 1000).
Literals (characters or numbers in SQL or PL/SQL)	Maximum size: 4000 characters	None
LONG	Maximum size: 2 GB - 1	Only one LONG column is allowed per table.
NCHAR	Maximum size: 2000 bytes	None
NCHAR VARYING	Maximum size: 4000 bytes	None
NCLOB	Maximum size: (4 GB - 1) * DB_BLOCK_SIZEinitialization parameter (8 TB to 128 TB)	The number of LOB columns per table is limited only by the maximum number of columns per table (that is, 1000).
NUMBER	999...(38 9's) x10125 maximum value -999...(38 9's) x10125 minimum value	Can be represented to full 38-digit precision (the mantissa) Can be represented to full 38-digit precision (the mantissa)
Precision	38 significant digits	None
RAW	Maximum size: 2000 bytes	None
VARCHAR	Maximum size: 4000 bytes	None
VARCHAR2	Maximum size: 4000 bytes	None

·         Physical Database Limits

Item	Type of Limit	Limit Value
Database Block Size	Minimum	2048 bytes; must be a multiple of operating system physical block size
Database Block Size	Maximum	Operating system dependent; never more than 32 KB
Database Blocks	Minimum in initial extent of a segment	2 blocks
Database Blocks	Maximum per datafile	Platform dependent; typically 222 - 1 blocks
Controlfiles	Number of control files	1 minimum; 2 or more (on separate devices) strongly recommended
Controlfiles	Size of a control file	Dependent on operating system and database creation options; maximum of20,000 x (database block size)
Database files	Maximum per tablespace	Operating system dependent; usually 1022
Database files	Maximum per database	65533 May be less on some operating systems Limited also by size of database blocks and by the DB_FILES initialization parameter for a particular instance
Database extents	Maximum per dictionary managed tablespace	4 GB * physical block size (with K/M modifier); 4 GB (without K/M modifier)
Database extents	Maximum per locally managed (uniform) tablespace	2 GB * physical block size (with K/M modifier); 2 GB (without K/M modifier)
Database file size	Maximum	Operating system dependent. Limited by maximum operating system file size; typically 222 or 4 MB blocks
MAXEXTENTS	Default value	Derived from tablespace default storage or DB_BLOCK_SIZE initialization parameter
MAXEXTENTS	Maximum	Unlimited
Redo Log Files	Maximum number of logfiles	Limited by value of MAXLOGFILES parameter in the CREATE DATABASEstatement Control file can be resized to allow more entries; ultimately an operating system limit
Redo Log Files	Maximum number of logfiles per group	Unlimited
Redo Log File Size	Minimum size	4 MB
Redo Log File Size	Maximum Size	Operating system limit; typically 2 GB
Tablespaces	Maximum number per database	64 K Number of tablespaces cannot exceed the number of database files because each tablespace must include at least one file
Bigfile Tablespaces	Number of blocks	A bigfile tablespace contains only one datafile or tempfile, which can contain up to approximately 4 billion ( 232 ) blocks. The maximum size of the single datafile or tempfile is 128 terabytes (TB) for a tablespace with 32 K blocks and 32 TB for a tablespace with 8 K blocks.
Smallfile (traditional) Tablespaces	Number of blocks	A smallfile tablespace is a traditional Oracle tablespace, which can contain 1022 datafiles or tempfiles, each of which can contain up to approximately 4 million (222) blocks.
External Tables file	Maximum size	Dependent on the operating system. An external table can be composed of multiple files.

·         Logical Database Limits

Item	Type of Limit	Limit Value
GROUP BY clause	Maximum length	The GROUP BY expression and all of the nondistinct aggregate functions (for example, SUM, AVG) must fit within a single database block.
Indexes	Maximum per table	Unlimited
Indexes	Total size of indexed column	75% of the database block size minus some overhead
Columns	Per table	1000 columns maximum
Columns	Per index (or clustered index)	32 columns maximum
Columns	Per bitmapped index	30 columns maximum
Constraints	Maximum per column	Unlimited
Subqueries	Maximum levels of subqueries in a SQL statement	Unlimited in the FROM clause of the top-level query 255 subqueries in the WHERE clause
Partitions	Maximum length of linear partitioning key	4 KB - overhead
Partitions	Maximum number of columns in partition key	16 columns
Partitions	Maximum number of partitions allowed per table or index	1024K - 1
Rows	Maximum number per table	Unlimited
Stored Packages	Maximum size	PL/SQL and Developer/2000 may have limits on the size of stored procedures they can call. The limits typically range from 2000 to 3000lines of code.
Trigger Cascade Limit	Maximum value	Operating system-dependent, typically 32
Users and Roles	Maximum	2,147,483,638
Tables	Maximum per clustered table	32 tables
Tables	Maximum per database	Unlimited

·         Process and Runtime Limits

Item	Type of Limit	Limit Value
Instances per database	Maximum number of cluster database instances per database	Operating system-dependent
Locks	Row-level	Unlimited
Locks	Distributed Lock Manager	Operating system dependent
SGA size	Maximum value	Operating system-dependent; typically 2 to 4 GB for 32-bit operating systems, and > 4 GB for 64-bit operating systems
Advanced Queuing Processes	Maximum per instance	10
Job Queue Processes	Maximum per instance	1000
I/O Slave Processes	Maximum per background process (DBWR, LGWR, etc.)	15
I/O Slave Processes	Maximum per Backup session	15
Sessions	Maximum per instance	32 KB; limited by the PROCESSES and SESSIONS initialization parameters
Global Cache Service Processes	Maximum per instance	10
Shared Servers	Maximum per instance	Unlimited within constraints set by the PROCESSES and SESSIONSinitialization parameters, for instance
Dispatchers	Maximum per instance	Unlimited within constraints set by PROCESSES and SESSIONSinitialization parameters, for instance
Parallel Execution Slaves	Maximum per instance	Unlimited within constraints set by PROCESSES and SESSIONSinitialization parameters, for instance
Backup Sessions	Maximum per instance	Unlimited within constraints set by PROCESSES and SESSIONSinitialization parameters, for instance

Oracle database 11.2.0.3 installation error: PRVF-5300, PRKC-1032, PRCT-1406

When installing Oracle database 11.2.0.3 on a Solaris database server, got the following error:


Oracle Database 11g Release 2 Installer


An internal error occurred within cluster verification framework


ERRORMSG(DBSERVER): PRVF-5300: failed to retrieve active version for CRS on this node
PRKC-1032: Directory /fs01/oracle/product/11.2.0/gird does not exist
PRCT-1406: Oracle Home location: /fs01/oracle/product/11.2.0/gird does not contain bin/srvctl

Oracle Support has a note on this:
Installation of Standalone (Non-RAC) 11.2.0 Database fails with errors: PRVF-5300, PRKC-1033, PRCT-1406 [ID 1380126.1]

Symptoms

When installing standalone (non-RAC) Database 11.2.0 software, it's failing with errors similar to:

oracle.cluster.verification.VerificationException: An internal error occurred within cluster verification framework
..
PRVF-5300 : Failed to retrieve active version for CRS on this node
PRKC-1033 : Executable /u01/app/oracle/product/11.2.0/grid/bin/olsnodes does not exist
PRCT-1406 : Oracle Home location: /u01/app/oracle/product/11.2.0/grid does not contain bin/srvctl

Changes

11gR2 Grid Infrastructure was installed on the server at some point in the past, but was later removed.

Cause

11gR2 Grid Infrastructure was not completely removed / de-installed, resulting in the existence of one or both of the following Grid Infrastructure files:

/etc/ocr.loc
/etc/oracle/olr.loc

Solution

Because the Grid Infrastructure files /etc/ocr.loc and/or /etc/oracle/olr.loc exist, the installer assumes it to be a RAC installation and tries to check the active CRS Services on the Server.  Those checks will fail because Clusterware (Grid Infrastructure) is no longer installed.

To resolve this situation:

1. Backup the files /etc/ocr.loc and /etc/oracle/olr.loc, then rename / delete them.
2. Retry the standalone (non-RAC) Database 11.2.0 installation.

upgrading Oracle database from 10.2.0.3se to 11.2.0.1se: ORA-00001: unique constraint (SYS.I_SYSTEM_PRIVILEGE_MAP) violated

Task: upgrading database 10.2.0.3se to 11.2.0.1se. The upgrading script was re-run after solving an error.

Error:
Got the following error when running Oracle Database 11.2 Post-Upgrade Status Tool after running Oracle upgrading script the second time:


Oracle Server
.   ORA-00001: unique constraint (SYS.I_SYSTEM_PRIVILEGE_MAP) violated
.   ORA-00001: unique constraint (SYS.I_SYSTEM_PRIVILEGE_MAP) violated
.   ORA-00001: unique constraint (SYS.I_SYSTEM_PRIVILEGE_MAP) violated
.   ORA-00001: unique constraint (SYS.I_SYSTEM_PRIVILEGE_MAP) violated
.   ORA-00001: unique constraint (SYS.I_SYSTEM_PRIVILEGE_MAP) violated
.   ORA-00001: unique constraint (SYS.I_SYSTEM_PRIVILEGE_MAP) violated
.   ORA-00001: unique constraint (SYS.I_SYSTEM_PRIVILEGE_MAP) violated
.   ORA-00001: unique constraint (SYS.I_SYSTEM_PRIVILEGE_MAP) violated
.   ORA-00001: unique constraint (SYS.I_SYSTEM_PRIVILEGE_MAP) violated
.   ORA-00001: unique constraint (SYS.I_SYSTEM_PRIVILEGE_MAP) violated
.   ORA-00001: unique constraint (SYS.I_SYSTEM_PRIVILEGE_MAP) violated
.   ORA-00001: unique constraint (SYS.I_SYSTEM_PRIVILEGE_MAP) violated
.   ORA-00001: unique constraint (SYS.I_SYSTEM_PRIVILEGE_MAP) violated
.   ORA-00001: unique constraint (SYS.I_SYSTEM_PRIVILEGE_MAP) violated
.   ORA-00001: unique constraint (SYS.I_SYSTEM_PRIVILEGE_MAP) violated
.   ORA-00001: unique constraint (SYS.I_SYSTEM_PRIVILEGE_MAP) violated
.   ORA-00001: unique constraint (SYS.I_SYSTEM_PRIVILEGE_MAP) violated
.   ORA-00001: unique constraint (SYS.I_SYSTEM_PRIVILEGE_MAP) violated
.   ORA-00001: unique constraint (SYS.I_SYSTEM_PRIVILEGE_MAP) violated
.   ORA-00001: unique constraint (SYS.I_SYSTEM_PRIVILEGE_MAP) violated
.   ORA-00001: unique constraint (SYS.I_SYSTEM_PRIVILEGE_MAP) violated
.   ORA-00001: unique constraint (SYS.I_SYSTEM_PRIVILEGE_MAP) violated
.   ORA-00001: unique constraint (SYS.I_SYSTEM_PRIVILEGE_MAP) violated
.   ORA-00001: unique constraint (SYS.I_SYSTEM_PRIVILEGE_MAP) violated
.                                         VALID      11.2.0.1.0  00:48:43

NOTE:

Oracle Note: ORA-00001: UNIQUE CONSTRAINT VIOLATED WHEN RUNNING THE POST UPGRADE STEP TO 11G [ID 1240775.1]

Cause

This is the expected behavior as confirmed by development in the unpublished bugs

Bug 5501515 TST&PERF VIOLATED SOME TABLE'S UNIQUE CONSTRAINT WHILE UPGRADING TO 11G
Bug 8834797 APPSST GSI 11G UNIQUE CONSTRAINT VIOLATED WHILE RUNNING CATUPGRD

There are 11g specific configuration rows to be inserted in the dictionary tables during the upgrade. When running multiple times the post upgrade step, the same rows are inserted again, therefore the unique constraint keys are violated.

Solution

Unique constraint errors are expected and acceptable on re-run of catupgrd.sql or utlu111s.sql. These ORA-1 errors can be safely ignored and should not impact the upgrade process in anyway.

ORA-00942 during database upgrade from 10.2.0.3 to 11.2.0.1 of Oracle Workspace Manager

Error: ORA-00942 during database upgrade from 10.2.0.3 to 11.2.0.1 of Oracle Workspace Manager

Environment: Solaris, Oracle 10.2.0.3se to 11.2.0.1se.

Got error when running @$ORACLE_HOME/rdbms/admin/utlu112s.sql after the upgrade:

Oracle Workspace Manager
.   ORA-00942: table or view does not exist
.   ORA-06512: at "WMSYS.OWM_MIG_PKG", line 1575
.   ORA-06512: at "WMSYS.OWM_MIG_PKG", line 1592
.   ORA-06512: at line 1
.                      VALID      11.2.0.1.0  00:01:54

Oracle document:

ORA-00942 during database upgrade of Oracle Workspace Manager [ID 1399508.1]

After the upgrade, dba_registry shows OWM is VALID, and there are no INVALID objects related to this component:

COMP_ID      STATUS      VERSION    COMP_NAME
------------ ----------- ---------- ----------------------------------------
CATALOG      VALID       11.2.0.3.0 Oracle Database Catalog Views
CATJAVA      VALID       11.2.0.3.0 Oracle Database Java Packages
CATPROC      VALID       11.2.0.3.0 Oracle Database Packages and Types
CONTEXT      VALID       11.2.0.3.0 Oracle Text
EXF          VALID       11.2.0.3.0 Oracle Expression Filter
JAVAVM       VALID       11.2.0.3.0 JServer JAVA Virtual Machine
ORDIM        VALID       11.2.0.3.0 Oracle Multimedia
OWM          VALID       11.2.0.3.0 Oracle Workspace Manager
RUL          VALID       11.2.0.3.0 Oracle Rules Manager
XDB          VALID       11.2.0.3.0 Oracle XML Database
XML          VALID       11.2.0.3.0 Oracle XDK

11 rows selected.

SELECT OWNER, OBJECT_NAME, OBJECT_TYPE
FROM DBA_OBJECTS
WHERE STATUS = 'INVALID'
ORDER BY OWNER, OBJECT_NAME, OBJECT_TYPE;

no rows selected

Cause

In pre-10g, WMSYS-owned objects could be in tablespaces other than SYSAUX.  Beginning with 10g, WMSYS-owned objects are now in SYSAUX.  Hence, as part of the database upgrade, wmsys.owm_mig_pkg.moveWMMetaData is run to move any WMSYS-owned objects from tablespace_X to SYSAUX.

Therefore, these errors can be ignored

BEGIN wmsys.owm_mig_pkg.moveWMMetaData; END;
*
ERROR at line 1:
ORA-00942: table or view does not exist
ORA-06512: at "WMSYS.OWM_MIG_PKG", line 1579
ORA-06512: at "WMSYS.OWM_MIG_PKG", line 1596
ORA-06512: at line 1
Because the pre-upgrade database is => Oracle 10g and all WMSYS objects are already in SYSAUX, i.e. there are no objects that need to be moved to SYSAUX.

Solution

The errors can be safely ignored.

ArcCatalog error: Failed to connect the specified server. Server library could not be loaded

When trying to make a direct connect to ArcSDE on 64 bit Solaris, the following error occurred:
Failed to connect ot database. Server library could not be loaded.

There is an ESRI document on this:

Error:  Failed to connect the specified server. Server library could not be loaded

Article ID:	36510
Software:	ArcGIS - ArcEditor 9.2, 9.3, 9.3.1 ArcGIS - ArcInfo 9.2, 9.3, 9.3.1 ArcGIS - ArcView 9.2, 9.3, 9.3.1 ArcSDE 9.2, 9.3, 9.3.1
Platforms:	N/A

Error Message

When using direct connect with ArcSDE on a 64-bit operating system, the following error message is encountered:

"Failed to connect the specified server. Server library could not be loaded."

Cause

Because ArcGIS Desktop is a 32-bit operating system application, it cannot work with applications created with 64-bit operating system libraries.

Solution or Workaround

Uninstall the Oracle Net Client 64-bit version and install the Oracle Net Client 32-bit version on the 64-bit operating system. Also, ensure the Oracle Net Client's full version matches the Oracle database's full version (for example, 10.2.0.4).

Still it is very hard to work around the error!