Oracle® Database

3.1 Upgrading a Database

Database Upgrade Assistant (dbua) is not supported in this release of Oracle 10g on OpenVMS. To upgrade a database, follow the steps outlined in ora_rdbms:readmemigvms.doc.

$ remoracle

3.2 Enabling Automated Backups

While installing Oracle Database, the Specify Backup and Recovery Options screen may appear truncated if the system does not have the required fonts installed. If the system has only fixed-width fonts, you may not be able to fully specify the required information in the Backup Job Credentials area of the screen. To work around this issue, do not select Enable Automated Backups on this screen. After the installation is complete, use Oracle Enterprise Manager 10g Database Control to enable automated backups.

3.3 Oracle interMedia

A known issue exists with Oracle interMedia on Oracle Database 10g. The problem may arise when making calls to mmtk_process() or mmtk_ext_process() in ordibody.sql, yielding errors such as the following:

ERROR at line 1:
   ORA-29400: data cartridge error 
   IMG-00714: internal error 
   ORA-28579: network error during callback from external procedure agent 
   ORA-06512: at "ORDSYS.ORDIMGEXTCODEC_PKG", line 164
   ORA-06512: at "ORDSYS.ORDIMGEXTCODEC_PKG", line 160
   ORA-06512: at line 1 
   ORA-06512: at "ORDSYS.ORDIMG_PKG", line 525
   ORA-06512: at "ORDSYS.ORDIMAGE", line 59
   ORA-06512: at "TKIDIUSER.IMG_PROCESSCOPY", line 12
   ORA-06512: at "TKIDIUSER.TKIDIPCU_MAIN", line 57
   ORA-06512: at line 1

The problem is being tracked internally by Oracle bug number 4203210.

3.4 DBCA Known Issues

You must use UNIX-based syntax when you specify file and path names. For example, the OpenVMS file specification dka100:[oracle10g.oradata.my_db]control1.ctl is expressed as the UNIX path dka100/oracle10g/oradata/my_db/control1.ctl.

3.5 CRS/RAC Known Issues

The following are known Cluster Ready Services (CRS) issues in the current release:

• In Oracle Database Administrator's Reference for hp OpenVMS Alpha (B13738-01), Appendix G, Section G.3, "Administering the Oracle Cluster Registry in RAC", step 5 should read as follows:

  5. Restart the CRS software on all the nodes in the cluster.

  You do not need to restart each node on OpenVMS systems.

• A CRS installation creates the following system level logicals:

  ORA_OCRCONFIG_LOC
  ORA_SCLS_SCR_PATH
  ORA_VAR_OPT
  
  

  If you plan to delete a CRS installation and create a non-CRS installation on the same node, ensure that you first deassign these logicals. Failure to do so will result in unintended errors or failures on assistants such as Oracle Net Configuration Assistant and Oracle Database Configuration Assistant.

• While installing CRS, the device on which an installation is created is visible and accessible across all nodes of a cluster installation. For example, for a CRS installation created on disk A to run on nodes B and C, disk A is accessible on both nodes. For this reason, it is not necessary to copy a device across nodes. You may see error messages similar to the following in the .err files created under the log directory of your orainventory:

  Error in copying file : rootadd.com
  oracle.ops.mgmt.cluster.ClusterException: PRKC-1004 : Problem in copying file to node
  
  

  These errors can be safely ignored.

• During a Custom installation of Oracle Real Application Clusters (RAC), Oracle Network Configuration Assistant (NETCA) is displayed at the end of the installation procedure even though the Database Creation option is not selected. You must run Virtual IP Configuration Assistant (VIPCA) before running NETCA for RAC. To do so, perform one of the following tasks:

  • Cancel the NETCA, and then run VIPCA, NETCA and Database Configuration Assistant (DBCA) in that order.

  • Run VIPCA from a separate window, then continue with NETCA that is displayed during custom installation, and then run DBCA.

• In the RAC database alert log files, messages similar to the following are displayed:

  SSKGXP_IP: Primary interface down
  operation
  location
  error error 0
  
  

  These messages are displayed if a private interconnect is not selected for RAC cluster communication, and the public IP address of the nodes are used for cluster communication. These messages can be ignored.

• While running srvctl or crs_* commands, you must specify the arguments to these commands. For example:

  srvctl start database "-d" "orcl"
  crs_stat "-p" "ora.ORCL.ORCL1.inst"
  
  

  Unlike Java, OpenVMS is case insensitive. Thus, the srvctl commands throws an error if the arguments are not passed with the right case. Moreover, the resource name you enter for crs_* commands should match the name it is registered with in the Oracle Cluster Registry (OCR).

• While running Virtual IP Configuration Assistant (VIPCA), tracing information is displayed on the terminal from where VIPCA is run. You can ignore this information. To suppress the tracing information, you must define the following logical before running VIPCA.

  define X$SRVM_TRACE X
  

3.6 TG4RDB Known Issues

The following are known Oracle Transparent Gateway for Rdb (TG4RDB) bugs in the current release:

• Bug 4417702: INCORRECT LOCATION OF TG4RDB.COM

• Bug 4435312: MISSING LOGICAL RDMS$RUJ IN TG4RDB RUNTIME ENVIRONMENT

• Bug 4435256: MISSING LOGICAL SYS$SCRATCH IN TG4RDB RUNTIME ENVIRONMENT

Oracle Transparent Gateway for Rdb fails to load because the TG4RDB.COM file is in an incorrect location or the runtime environment does not contain the logicals RDMS$RUJ and SYS$SCRATCH. This causes the gateway to generate the following runtime error:

ORA-28500: connection from ORACLE to a non-Oracle system returned this message:

Transparent gateway for RDB]tm_rollback_from_failure: Heuristic roll back: trying all tdps, ignoring failure

A patch that fixes all three bugs is available from OracleMetaLink. Download and apply the patch before configuring Oracle Transparent Gateway for Rdb.

http://metalink.oracle.com/

3.7 Known Issues Related to Database Limits

The following known issues are related to Oracle Database 10g file size limits:

In Oracle Database Administrator's Reference for hp OpenVMS Alpha (B13738-01), Chapter 1, Section 1.3, "Database Limits", Table 1-1 should read as follows:

3.8 CXXLINK Error Message

C++ links in the installation linking phase will generate the following error, which can be safely ignored:

%CXXLNK-I-NODEMANGLER, No demangler database was found; unresolved symbols will not be demangled.

3.9 Enhanced Oracle Performance

Install Oracle image as an OpenVMS resident image to increase the performance of Oracle. To install the Oracle.exe image resident, the following changes need to be made to OpenVMS and Oracle.

Oracle recommends you to do initial testing in a non-production environment whenever possible. For queries, contact your local support organization.

3.10 Known Problems

The following are known problems in the current release:

• Bug 3107086: RMAN backup files not truncated when finished

• Bug 1835885: DBV fails with DBV-00102 on data files exceeding 2047 MB

• Bug 3437279: SQL*LOADER fails with ORA-01426: Numeric Overflow

• Bug 807591: ORA-00600 [KCCSBCK FIRST] [1] [1856240794] IN TKMSTU9E.DIF

  The effect of this bug will include: an Exclusive Mount attempt when another Instance is already Mounted fails with Split Brain ORA-00600 [KCCSBC FIRST] instead of a file lock conflict.

• Bug 3436862: (4L1) TKAMX384.DIF - ORA-16107: ALL LOG DATA FROM PRIMARY HAS BEEN PROCESSED

  The effects of this bug include:

  • When Initialization parameter STANDBY_FILE_MANAGEMENT is MANUAL and the DBA forgets to manually copy a new data file to the Standby database after adding a data file to the Primary, the Apply server will not detect the omission and terminate.

  • ORA-27086 or ORA-27089 may not be detected.

• Bug 3403376: TRLE2BX.DIF AND TRLE2VX.DIF FROM LRG3CU ON LINUX

  This problem will be fixed in a future release. The effect of this bug will include: if a data file contains binary data which may be interpreted as a record terminator, SQL*Loader may miss a record terminator.

• Bug 4420104: Temporary files PERLPIPE*.COM created in login directory

  This has no impact on the functioning of the EMAgent. The temporary files can be manually deleted. Refer to the bug for more details and latest updates.

• Bug 4420463: Delays in Listener Start/Stop from Console

  This problem has not been observed in an Oracle installation, but has only been observed within the internal test QA area, which was set up with additional spooling of debugging information. However, the latency may reproduce in a customer environment, although very unlikely. To correct this, repeat the operation or perform the operation directly on the Server box where the listener is running. The modified status is automatically picked by the EM console within a few minutes of the direct operation.

• Bug 4420395: Inconsistent ora-0600 errors during RAC stress test

• If you select 'Generate Database Create Scripts' when running the Database Configuration Assistant, then error messages similar to the following are displayed:

  P2-0310: unable to open file
  "DISK:[INSTALL_TEST.DHAYTER.Home15]/sysman/admin/emdrep/sql/core/latest/admin/admin_check_repos_user.sql"
  
  SP2-0310: unable to open file
  "DISK:[INSTALL_TEST.DHAYTER.Home15]/sysman/admin/emdrep/sql/core/latest/admin/admin_create_repos_user.sql"
  
  

  These errors can be safely ignored. It is not required to create a repository on OpenVMS, since the DBConsole product is not supported.

• When performing an Oracle Database Custom installation, the following message may appear in the ora_root:[admin.sid.create]JServer.log file:

  1 :ORA-06512: at "SYS.DBMS_JAVA", line 236
  1 :ORA-06512: at line 2
  1 :ORA-29558: JAccelerator (NCOMP) not installed. Refer to Install Guide for instructions.
  
  

  This message can be safely ignored as the JAccelerator component is not supported.

• Bug 4498601: OUI unable to find any user group

  During installation, the following error is reported by the OUI at 84% (during Processing Oracle Database 10g 10.1.0.3.0):

   Unable to find any user group
  
  

  The installActions log file contains the following :

  Calling Query unixQueries10.1.0.3.0  getGroups 
  Query Exception: NoGroupsException
  Query Exception Class: class oracle.sysman.oii.oiil.OiilQueryException 
  
  

  This occurs when the installation is carried out from an OpenVMS account, which is a member of an unnamed UIC group. Before attempting to install Oracle 10g Release 1 products, you are advised to execute the following commands:

  $ grp = 'f$getjpi("","GRP")' * %X10000
  $ grp = grp + %X0FFFF
  $ grpname = f$identifier(grp,"NUMBER_TO_NAME")
  $ show sym grpname
  
  

  If the symbol grpname above is a null string then

  $ write sys$output f$fao("!%U",grp)
  
  

  This command displays a group UIC in a format similar the following:

  [50,*]
  
  

  Use the VMS AUTHORIZE utility to add a group name to the VMS rights database.

  For example, the following commands use the UIC [50,*] and the group name DBA.

  $ set default sys$system
  $ run authorize
  UAF> add/identifier/value=uic:[50,*] DBA
  %UAF-I-RDBADDMSGU, identifier DBA value [000050,177777] added to rights database
  UAF> exit
  

4.1 NetCA Help

In the Oracle Net Configuration Assistant (NetCA) help, the link to the Select Oracle Context help topic is broken. The text for this topic is as follows:

Directory Usage Configuration, Select Oracle Context

Oracle administrative content has been found in more than one location in the directory. Oracle administrative content is stored in Oracle Context, a subtree in the directory that stores Oracle entries.

From the list, select or enter the location you want to use as the default Oracle Context location from which this computer will access Oracle entries, such as connect identifiers.

4.2 NetCA IPC Protocol

If you select the use of the IPC protocol for the network layer, NetCA cannot reliably determine whether or not the key value specified in the protocol is in use. To let the user specify whether or not the key is actually available, NetCA displays the following message:

The information provided for this listener is currently in use by other software on this computer. You can proceed with this configuration as it is, but it will not be possible to start this listener until the conflict is resolved. Would you like to continue with the configuration anyway?

When this message is displayed, you should check if there are other listener processes on the system. In addition, you should ensure that the key value you have specified is not already in use. If it is not in use, then proceed with the configuration session. If it is in use, then shut down the listener using the key. Alternatively, you can use the NetCA screen to specify that you do not want to continue with the installation and then select a key value that is not in use on the system.

4.3 Flashback Table or Flashback Analysis

If a user starts the Flashback Table or Flashback Analysis operation, and that user has FLASHBACK ANY TABLE privileges but does not have DBA privileges and specific flashback privileges on the objects that flashback is started on, then the following errors may occur:

ORA-02002: error while writing to audit trail 
ORA-00600: internal error code, arguments: [kzasps1], [4], [47], [],[],  

To fix this problem, as SYSDBA, grant the user FLASHBACK privilege on the objects that are referred to in the FLASHBACK TABLE statement and then start the flashback operation. For example:

SQL> GRANT FLASHBACK ON SCOTT.EMP_1 TO user1;

This issue is tracked through Oracle bug 3403666.

4.4 Error When Viewing Period SQL Execution Plan in Korean

Viewing the execution plan of Period SQL in Korean causes an internal server error. This problem is unique to Korean, and does not reproduce in Japanese or Chinese. The only workaround currently available is to run the product in a language other than Korean when you need to view this page.

4.5 Grid Features

Oracle Database New Features for Oracle Database 10g release 1 (10.1) lists two Grid features that are not available in the first release of Oracle Database 10g: Resonance and Transparent Session Migration.

4.6 Installing Enterprise Security Manager

To install Enterprise Security Manager (ESM), install Oracle Client and choose the Administrator installation type.

4.7 Full-Text Searching with Oracle Text

For full-text searching with Oracle Text, you must create XML tables manually.

If you will need to use Oracle Text indexes for text-based ora:contains searches over a collection of XML elements, then do not use the XML schema annotation storeVarrayAsTable="true". This annotation causes element collections to be persisted as rows in an Index Organized Table (IOT). Oracle Text does not support IOTs.

To be able to use Oracle Text to search the contents of element collections, set parameter genTables="false" during schema registration. Then create the necessary tables manually, without using the ORGANIZATION INDEX OVERFLOW clause. The tables will then be heap-organized instead of index-organized (IOT), as shown in the following example:

CREATE TABLE PurchaseOrder of XMLTYPE
  XMLSCHEMA http://localhost:8080/home/SCOTT/poSource/xsd/purchaseOrder.xsd
  ELEMENT "PurchaseOrder"
  VARRAY "XMLDATA"."ACTIONS"."ACTION"
    STORE AS TABLE ACTION_TABLE ((PRIMARY KEY 
       (NESTED_TABLE_ID, ARRAY_INDEX)))
  VARRAY "XMLDATA"."LINEITEMS"."LINEITEM"
     STORE AS TABLE LINEITEM_TABLE ((PRIMARY KEY 
       (NESTED_TABLE_ID, ARRAY_INDEX)));

4.8 Transport Layer Security

In this release, the AES_128 and AES_256 cipher suites do not work with Transport Layer Security (TLS). This issue is tracked through Oracle bug 3753967.

4.9 Oracle Net Configuration Files

Files such as LISTENER.ORA, TNSNAMES.ORA, SQLNET.ORA, if configured manually, or copied and edited from earlier releases of Oracle Database may have record attributes that are incompatible with Oracle Database 10g release 1 (10.1.0.3.0). The software cannot read such files.

This may result in:

• Inability to start the listener

• Services not registered with the listener

• Inability to connect to other databases

• ORA-12154: TNS:could not resolve service name

Run the following command on each file affected:

$ DIR/FULL filename;0

An output similar to the following may be displayed:

Record format:      Variable length, maximum 255 bytes
Record attributes:  Carriage return carriage control

If the output includes the preceding entries, then run the following command:

$ CONVERT/FDL=SYS$INPUT filename filename
RECORD
 CARRIAGE_CONTROL carriage_return
 FORMAT stream_LF
^Z