Tuesday Feb 04, 2014

Master Note for Database Startup/Shutdown (Doc ID 1270450.1)


During Startup, the instance is started first (nomount stage) which then mounts the database by accessing the control files specified in the CONTROL_FILES parameter. The next step will be to open the database which includes opening the datafiles and redo log files. Applying the redo (rollforward) and the rollback of uncommitted data (rollback) also happens if the previous shutdown was not a clean one (shutdown normal or immediate).

Similarly the database and instance undergoes multiple phases during shutdown. First the database is closed ie, the datafiles and the redolog files are closed. Then the database will be dismounted  to disassociate it from the instance. After a database is unmounted, Oracle Database closes the control files of the database. The next step will be to shutdown the instance by removing the SGA from the memory and terminating the background processes.

There are various shutdown modes such are normal, immediate,transactional and abort. When a database is closed as part of a SHUTDOWN with any option other than ABORT, Oracle Database writes data in the SGA to the data files and online redo log files. If a SHUTDOWN ABORT or abnormal termination occurs, then the instance of an open database closes and shuts down the database instantaneously. Oracle Database does not write data in the buffers of the SGA to the data files and redo log files. The subsequent reopening of the database requires instance recovery, which Oracle Database performs automatically.

Database startup and shutdown are powerful administrative options that are restricted to users with administrator privileges.

For details you can refer Note 1505155.1 - Master Note: Overview of Database Startup and Shutdown

Common Issues During Database Startup

This Section list out the common issues encountered during startup. The error can be reported in any of the above mentioned phases like nomount,mount or open. Since transaction recovery continues even after opening the database, you may observe issues like hang, high CPU usage etc, even after the database is open. The documents mentioned in the below section can be specific to platform or database versions.

Startup upgrade/migrate or setting _system_trig_enabled = FALSE will disable startup triggers to rule out startup trigger problems.

12c Startup/Shutdown

Startup and shutdown of the container database is the same as it has always been for regular instances. 

For PDBs

Also Refer to the following documents for more information on 12c Startup and Shutdown: 
  • Note 1582453.1 When to use startup / shutdown database and alter database command in 12c

ORA-27102 Errors

ORA-27102 errors normally occurs due to memory issues.The Common causes could be due to Semaphore Kernel misconfigurations,Memory related Ulimit settings,RAM or swap configurations.

ORA-27300 Errors

These errors are generally reported when the Operating System called for error or when there was a connection killed or a network interconnection failures or an OS configuration issue.The error ORA-27300 will also be accompanied by ora-27301 and ora-27302

Note 579365.1 Troubleshooting ORA-27300 ORA-27301 ORA-27302 errors

ORA-64 Errors

This error could occur when the database init.ora parameter calling for more resources than the Operating System is configured to provide.The parameters could be PROCESSES,DB_BLOCK_SIZE,SGA and more.

Note 1457812.1 ORA-00064 Error Reported After Increasing Processes Parameter value

ORA-27123 Errors

Note 115753.1 UNIX: Resolving the ORA-27123 error

ORA-1081 Errors

This error could occur when we try to startup an instance that is already running or if the shared segments/semaphores already exist.

Note 1010214.6 ORA-1081: Starting Instance
Note 18657.1 OERR: ORA 1081 cannot start already-running Oracle - shut it down first

NFS Related Issues

Note 8418190.8 Bug 8418190 - Direct NFS warnings during database startup
Note 236794.1 NFS Locking Problems Encountered During Database Startup
Note 1430654.1 Database Startup Failed with "Direct NFS: please check that oradism is setuid"
Note 430920.1 NetApp: Using 'nolock' NFS Mount Option with non-RAC Systems Results in Database Corruption

Transaction Recovery Slowness

There could be slowness in the database during the open phase when the database is busy performing transaction recovery.

Note 1494886.1 Database Transaction Recovery
Note 414242.1 Database Hangs Because SMON Is Taking 100% CPU Doing Transaction Recovery
Note 12934890.8 Bug 12934890 - Startup hangs waiting for row cache lock due to open transaction against UNDO$

ORA-704 Errors

This is a general error reported at startup when there is some problem during processing of bootstrap information.There should be an accompanying error/s. Plug the ORA=704 and the other errors it reports into the Oracle Support search engine for a solution.

ORA-9968 Errors

There are some client shadow processes hanging. Although the lk< SID> file is deleted the hanging processes still have a lock on the open file handle. This prevents the database to startup although a new lk<SID> file can be created successfully. An oracle process (background or shadow process) that exists while the instance is not started (crashed or not cleanly stopped) can have a lock on a file while this file is actually removed from the system. This is because on UNIX there is still a lock on the open file handle.

Note 160395.1 Database Startup Fails with ORA-1102 and ORA-9968
Note 1488147.1 Instance Startup Raises Error ORA-09968: unable to lock file (Doc ID 1488147.1)

ORA-12547 Errors

The error ORA-12547 indicates that the communication channel has been broken. It's most often thrown because the other end of the process went away unexpectedly.

Note 1307075.1 Oracle Database Fails to Start with Error ORA-12547
Note 381566.1 connect / as sysdba Fails with Ora-12547 And Tns-12514
Note 744512.1 Ora-12547: Tns:Lost Contact Creating Database After Clean Installation

ORA-1157 Errors 

The background process was not able to find one of the datafiles.The database will prohibit access to this file but other files will be unaffected.However, the first instance to open the database will need to access all online datafiles.Accompanying messages from the operating system will describe why the file was not found.

Note 184327.1 ORA-1157 Troubleshooting

Common Errors / Issues During Database Shutdown

The most common issue observed while bringing down the database is shutdown immediate hang. The main reasons for Shutdown immediate hang is:
- processes still continue to be connected to the database and do not terminate.
- SMON is cleaning temp segments or performing delayed block cleanouts.
- Uncommitted transactions are being rolled back.

The below section provides the consolidated list of known issues during shutdown. The documents mentioned in the below section can be specific to platform or database versions.

Transaction Recovery

Note 375935.1 What To Do and Not To Do When 'shutdown immediate' Hangs
Note 1076161.6 Shutdown Normal or Shutdown Immediate Hangs. SMON disabling TX Recovery
Note 414242.1 Database Hangs Because SMON Is Taking 100% CPU Doing Transaction Recovery
Note 100054.1 Transaction Rollback after a failed operation or during Database Shutdown

ORA-24324 Errors

Note 794293.1 ORA-24324 During Shutdown


Note 1001248.1 On Solaris 9 Systems, Oracle Shutdown May Hang If Utilizing Dynamic Initmate Shared Memory (DISM) 

Issues specific to automatic shutdown and startup

This section is specific to the automatic shutdown and startup that can be configured with the dbora / dbshut / dbstart scripts.

Automatic Startup Failure

The key to diagnosing automatic startup failures is to determine where startup fails. This can be done via the following steps:

  1. Determine if instance starts manually as Oracle software owner.
  2. Determine if instance starts via dbstart command run as Oracle software owner.
  3. Determine if instance starts when root runs following dbstart command:
    su - $ORA_OWNER -c $ORA_HOME/bin/dbstart

    where $ORA_OWNER is set to Oracle software owner.
  4. Determine if instance starts when running as root the OS script which calls dbstart, ie "/etc/init.d/dbora start". NOTE: Running via sh -x command will show each command as it is run from script to better see what is going on.
  1. #> sh -x /etc/init.d/dbora start

Automatic Shutdown Failure

As with automatic startup, the key to diagnosing automatic shutdown failures is to determine where shutdown fails. This can be done via following steps:

  1. Determine if instance stops manually as Oracle software owner.
  2. Determine if instance stops via dbshut command run as Oracle software owner.
  3. Determine if instance stops when root runs command
    su - $ORA_OWNER -c $ORA_HOME/bin/dbshut
    where $ORA_OWNER is set to Oracle software owner.
  4. Determine if instance stops when running as root the OS script which calls dbshut, ie "/etc/init.d/dbora stop". NOTE: Running via sh -x command will show each command as it is run from script to better see what is going on.
    #> sh -x /etc/init.d/dbora stop

Further Diagnostics

If you were not able to resolve the issue with the details provided in this document, please raise a Service Request for further assistance from Oracle Support. The diagnostic information required to troubleshoot the issue is listed in the below document:

Troubleshooting Database Startup/Shutdown Problems (Doc ID 851057.1).


NOTE:1505155.1 - Master Note: Overview of Database Startup and Shutdown

Monday May 16, 2011

Troubleshooting ORA-1555 (Doc ID 1307334.1)

This article is intended to assist in finding tips and techniques to assist with finding solutions to ORA-1555 errors. The document will cover the following topics:

Common Causes/Solutions


The ORA-1555 errors can happen when a query is unable to access enough undo to build
a copy of the data at the time the query started. Committed “versions” of blocks are
maintained along with newer uncommitted “versions” of those blocks so that queries can
access data as it existed in the database at the time of the query. These are referred to as
“consistent read” blocks and are maintained using Oracle undo management.

See Note 40689.1 - ORA-1555 "Snapshot too old" - Detailed Explanation for more about
these errors.


Due to space limitations, it is not always feasible to keep undo blocks on hand for the life of the instance. Oracle Automatic Undo Management (AUM) helps to manage the time frame that undo blocks are stored. The time frame is the “retention” time for those blocks.

There are several ways to investigate the ORA-1555 error. In most cases, the error is a legitimate problem with getting to an undo block that has been overwritten due to the undo “retention” period having passed.

AUM will automatically tune up and down the “retention” period, but often space limitations or configuration of the undo tablespace will throttle back continuous increases to the “retention” period.

The error message is reported in the user session and often is not captured in the alert log. The user could see a message like

Using rollback segment functionality:
ORA-1555: snapshot too old (rollback segment too small)


Using AUM:
ORA-01555: snapshot too old: rollback segment number 9 with name "_SYSSMU9$" too small

If the error is captured in the alert.log, you would see something like

Tue May 26 16:16:57 2009
ORA-01555 caused by SQL statement below (SQL ID: 54yn3n36w24ft, Query Duration=922 sec, SCN: 0x0007.8a55f4e3)

Initial Investigation

Rollback Segments:
With Oracle 10g and later versions of Oracle, you can still use a Rollback Segments configuration. ORA-1555 errors in that environment still follow older guidelines as described in

Note 10579.1 - How many Rollback Segments to Have
Note 107085.1 - Tuning Rollback Segments
Note 69464.1 - Rollback Segment Configuration & Tips
Automatic Undo Management:
The database will be self tuning for undo when using Automatic Undo Management. This does not eliminate ORA-1555 completely, but does minimize ORA-1555 as long as there is adequate space in the undo tablespace and workloads tend to follow repeatable patterns. In some cases with periodic changes to workload (large data updates particularly with LOB data) the self tuning of undo can become aggressive and lead to undo issues.

Note 461480.1 - FAQ Automatic Undo Management (AUM) / System Managed Undo (SMU)
Note 135053.1 -How to Create a Database with Automatic Undo Management
Note 268870.1 - How to Shrink the datafile of Undo Tablespace
Note 231776.1 - How to switch a Database from Automatic Undo Management (AUM) back to using Rollback Segments
Note 296863.1 - How to Keep All UNDO Segments from Being Offlined in Oracle 10g - Fast Ramp-Up
LOB Issues:
Out-of-row LOB undo is maintained in the LOB segment. So the UNDO tablespace and undo retention is not associated with most LOB ORA-1555 issues. Instead the LOB column is created using either PCT_VERSION or RETENTION to manage how much space within blocks or time transpires before the LOB undo is overwritten. In environments with high updates, deletes on rows including LOBs, the chances of ORA-1555 on LOB undo is very high.

PCT_VERSION and RETENTION are not auto-tuned. To “tune” those configuration settings, you must change the values for PCT_VERSION or RETENTION. Changes to UNDO_RETENTION does not change LOB retention time frames.

Note 162345.1 - LOBS - Storage, Read-consistency and Rollback
Note 386341.1 - How to determine the actual size of the LOB segments and how to free the deleted/unused space above/below the HWM
Note 563470.1 – Lob retention not changing when undo_retention is changed
Note 422826.1 – How to identify LOB Segment Use PCTVERSION or RETENTION from Data Dictionary

Error Tracing

Undo error tracing can be done for normal undo operations using the following events:

NOTE: Normal undo operations will be indicated in the error message in that the error message includes a segment name like

…. name "_SYSSMU1$" too small

If the error doesn’t show a segment name

… name "" too small

the problem is often related to LOB undo
If using pfile:

event="10442 trace name context forever, level 10"

If using spfile:

Alter system set events '10442 trace name context forever, level 10';

Reproduce the ORA-1555 error and upload the trace file to Oracle Support.

LOB undo error tracing is more difficult. Set additional tracing events as follows:

Start Session 1
Alter session set events '10046 trace name context forever, level 12';
Reproduce the error
Exit Session 1

Start Session 2
Alter session set events '10051 trace name context forever, level 1';
Reproduce the error
Exit Session 2

Start Session
Alter session set events '1555 trace name errorstack forever, level 3';
Reproduce the error
Exit Session 3

Additional resources to review:
Note 846079.1 – LOBs and ORA-1555 troubleshooting
Note 253131.1 –Concurrent Writes May Corrupt LOB Segment When Using Auto Segment Space Management
Note 467872.1 – TROUBLESHOOTING GUIDE (TSG) – ORA-1555


The V$UNDOSTAT view holds undo statistics for 10 minute intervals. This view
represents statistics across instances, thus each begin time, end time, and
statistics value will be a unique interval per instance.

This does not track undo related to LOB
Note 262066.1 – How To Size UNDO Tablespace For Automatic Undo Management
Note 1112363.1 – When Does Undo Used Space Become Available?

Diagnostics Scripts

Refer to Note 746173.1 : Common Diagnostic Scripts for AUM problems
and Note 877613.1 : AUM Common Analysis/Diagnostic Scripts

Common Causes/Solutions

Using Rollback Segments functionality:

* Problem happening on SYSTEM tablespace that still uses old Rollback Segment functionality even when configured for Automatic Undo Management (AUM).

* There are not enough rollback segments to manage the undo needed for long running queries.

* Rollback Segments are too small and undo is overwritten before long running queries complete.
Note 69464.1 – Rollback Segment Configuration & Tips
Note 10630.1 – ORA-1555: “Snapshot too old” – Overview
Note 862469.1 – ORA-604 & ORA-1555 Rollback Segment 0 with Name “System” Too Small

Using Automatic Undo Management (AUM):

* TUNED_UNDORETENTION in V$UNDOSTAT around the time of the error is lower than the QUERY DURATION indicated in the error message. This is a legitimate ORA-1555 and if queries are going to run for very long time frames, UNDO_RETENTION may need to be larger. Auto-tuned retention may not be able to keep up with the undo workload and staying within space limitations on the UNDO tablespace.

* LOB updates and/or deletes are frequent and a higher PCT_VERSION is required to provide enough space in the LOB Segment to accommodate the LOB undo. RETENTION on LOBs that are updated or deleted frequently can run into problems holding UNDO long enough for queries.

* QUERY DURATION shown in the error message is 30+ years and therefore, no amount of undo will satisfy the consistent read blocks.

Note 750195.1 – ORA-1555 Shows Unrealistic Query Duration (billions of seconds)

* QUERY DURATION shown in the error message is 0. NOTE: This has been filed as a bug on many release levels and has been very difficult to narrow down to a specific problem.

Note 761128.1 – ORA-1555 Error when Query Duration as 0 Seconds

* QUERY DURATION is lower than TUNED_UNDRETENTION. Undo header information can sometimes get overwritten or you could be seeing a bug.

* TUNED_UNDORETENTION stays very high and UNDO tablepsace continues to grow continuously or getting space errors.

Note 1112431.1 – Undo Remains Unexpired When Using Non-autoextensible Datafiles for Undo Tablespace.

Additional Reference:

Database Administration Community

Wednesday Nov 17, 2010

Oracle Support Master Note for Troubleshooting Managed Distributed Transactions (Doc ID 100664.1)

[Read More]

Oracle Support Master Note for Troubleshooting Streams Apply Errors ORA-1403, ORA-26787 or ORA-26786 (Doc ID 265201.1)

[Read More]

Oracle Support Master Note for Troubleshooting Streams Capture 'WAITING For REDO' or INITIALIZING (Doc ID 313279.1)

[Read More]

Oracle Support Master Note for Streams Setup Scripts (Doc ID 789445.1)

[Read More]

Oracle Support Master Note for Streams Performance Recommendations (Doc ID 335516.1)

[Read More]

Sunday Jul 04, 2010

Oracle Gateway Master Note (Doc ID 1083703.1)

Master Note for Oracle Gateway Products

1. Concepts and Availability

Oracle Gateway products are based on Heterogeneous Services and allow access to non-Oracle databases from Oracle products.
Heterogeneous Services provides the generic technology for connecting to non-Oracle systems. As an integrated component of the database, Heterogeneous Services can exploit features of the database, such as the powerful SQL parsing and distributed optimization capabilities.
Heterogeneous Services extend the Oracle SQL engine to recognize the SQL and procedural capabilities of the remote non-Oracle system and the mappings required to obtain necessary data dictionary information.

There are dedicated Gateways for the following non-Oracle data sources -
- Microsoft SQL*Server - Database Gateway for SQL*Server (DG4Msql)
- Sybase - Database Gateway for Sybase (DG4Sybase)
- Informix - Database Gateway for Informix (DG4Ifmx)
- IBM DB2 - Database Gateway for DRDA (DG4DRDA)
- Teradata - Database Gateway for Teradata (DG4Teradata)
- Websphere MQ - Database Gateway for Websphere MQ (DG4MQ)
- Remote online transaction processors (OLTPs) - Database Gateway for APPC (DG4APPC)
- IMS - Database Gateway for IMS (DG4IMS)
- VSAM - Database Gateway for VSAM (Dg4VSAM)
- Adabas - Database Gateway for Adabas (DG4Adabas)

Non-Oracle datasources for which a dedicated gateway is not available can be accessed by using the following -

Database Gateway for ODBC (DG4ODBC)

which uses third party ODBC drivers to make the connection to non-Oracle data sources such as as MySQL, Progress, Ingres.
It can also be used to access non-Oracle databases for which a dedicated gateway is available.
Further details are available in this note -

Note.233876.1 Options for Connecting to Foreign Data Stores and Non-Oracle Databases - For example - DB2, SQL*Server, Sybase, Informix, Teradata, MySQL

There are differences in the functionality and licensing of the Database Gateway for ODBC and the other gateways which are discussed in these notes -
Note.252364.1 Functional Differences Between Generic Connectivity and Database Gateways
Note.232482.1 Gateway and Generic Connectivity Licensing Considerations

The following note has information about the desupport of earlier gateway versions -

Note.549796.1 Desupport of Oracle Transparent Gateways
Note.353723.1 Oracle Transparent Gateway for iWay
Note.353728.1 Oracle Transparent Gateway for INGRES
Note.353725.1 Oracle Transparent Gateway for Rdb
Note.353729.1 Oracle Transparent Gateway for RMS
Note.417250.1 Oracle Transparent Gateway for INFORMIX
Note.417253.1 Oracle Transparent Gateway for SYBASE
Note.417254.1 Oracle Transparent Gateway for MS SQL Server
Note.417251.1 Oracle Transparent Gateway for TERADATA
Note.420436.1 Oracle Transparent Gateway for DRDA - SNA Support desupport
Note.559947.1 Oracle Access Manager for AS/400
Note.559948.1 Oracle Transparent Gateway for DB2/400

Oracle's Software Error Correction Support policy document is available in this note -

Note.209768.1 Database, FMW, EM Grid Control, and OCS Software Error Correction Support Policy

Oracle's Lifetime Support Policy document is available here:


For information about the Gateway support policy refer to the section -

Oracle Gateway Release's

The certification matrix for the 11.1 and 11.2 Gateways is now available on OTN from the following URL -


then -

Database Gateways Certification Matrix (PDF)
Mainframe Database Gateways Certification Matrix (PDF)
Legacy Database Gateways Certification Matrix (PDF)

Please note that the Legacy Gateways -

can no longer be ordered. They will still be available on install media but will be decommissioned.

2. Downloading Gateway Products

Before trying to download a Gateway please refer to the certification matrix to make sure it is available for your platform and version.

Oracle Gateway products can be downloaded from the following -

1. Oracle Technology Network - OTN -


Choose the relevant platform and version then the 'See All' option.
Under that there will be an option to download the Gateway products, for example -

Oracle Database Gateways 11g Release 2 ( for Microsoft Windows (32-bit)

Please note that only 11.2 versions of the Gateway products are available on Windows 64-bit.  The earlier versions are not available on that platform.

2. Oracle Software Delivery Cloud


- go through the Terms & Restriction proces
- on the next screen ' Media Pack Search' screen choose -
 Select a Product Pack - Oracle database
- then choose your platform
- choose the 'Oracle database' media pack for the version you need - 11.1 or 11.2
- on the next screen there will be a gateway media pack to download.

The following note has links to a video showing how to download gateways -

Note.1279746.1 Where Can I Find And Download the Latest Gateways Available From Oracle?

3. My Oracle Support - and

The  and versions of the gateways are included in the Oracle Database patch sets 10098816 and 10404530.
Starting with the patch set, Oracle Database patch sets are full installations of the Oracle Database software. This means that you do not need to install a release of a gateway  before installing the or versions. The later versions can be installed in completely separate ORACLE_HOME directories from any existing installs.
To download the latest gateways -

- logon to My Oracle Support
- go to Patches & Updates section
- search for patch number 10404530 and choose your platform
- click on the patch number
- for most platforms for the gateways you only need to download -
for example -
but for Windows 32-bit this is -

To confirm which file is needed for the Gateways review the 'README' file which details which download files contain which software.

The patch is also available for some platforms and can be found as patch 10404530 on My Oracle Support.

3. Installation and Configuration

The installation and configuration for each gateway is described in the documentation.
This is available from -


Click on the version required - 11.1 or 11.2  - then 'View Library'
The Gateway documentation is available from the 'Information Integration' option under the 'Heterogeneous Connectivity' heading.

The following note gives an overview of the Gateway install process -

Note.1351618.1 Installation Overview For Oracle Database Gateway Products

There are also notes available in My Oracle Support (MOS) to help with the install and configuration -

- logon to MOS -


- Knowledge tab
- Oracle Database Products
- Oracle Database
- Gateways
- then choose the relevant gateway

Examples are -

Note.437374.1 How to Configure DG4MSQL (Oracle Database Gateway for MS SQL Server) Release 11 on Linux x86 32bit post install
Note.466267.1 How to Configure DG4MSQL (Database Gateway for MS SQL Server) on Windows 32bit post install
Note.562509.1 How to Configure DG4MSQL (Oracle Database Gateway for MS SQL Server) 64bit Unix OS (Linux, Solaris, AIX,HP-UX) post install
How to Configure DG4MSQL (Database Gateway for MS SQL Server) on a 64bit Windows post install
Note.466228.1 How to Configure DG4ODBC on Linux x86 32bit to Connect to Non-Oracle Databases post install
Note.561033.1 How to Configure DG4ODBC on 64bit Unix OS (Linux, Solaris, AIX, HP-UX) to Connect to Non-Oracle Databases Post Install
Note.466225.1 How to Configure DG4ODBC (Oracle Database Gateway for ODBC) on Windows 32bit to Connect to Non-Oracle Databases Post Install
Note.1266572.1 How to Configure DG4ODBC (Oracle Database Gateway for ODBC) on 64bit Windows Operating Systems to Connect to Non-Oracle Databases Post Install
Note.945879.1 How to Setup DG4DRDA (Oracle Database Gateway for DRDA) Release 11.2 on Unix (Linux, AIX, HP-UX Itanium and Solaris) to Connect to DB2
Note.1086359.1 How to Setup DG4DRDA (Oracle Database Gateway for DRDA) on Windows x86 (32bit and 64bit) to Connect to DB2
Note.437689.1 How to Setup DG4IFMX (Oracle Database Gateway for Informix) Release 11 on Linux
Note.437696.1 How to Setup DG4SYBS (Oracle Database Gateway for Sybase) Release 11 on Linux
Note.554402.1 How to Setup DG4TERA (Oracle Database Gateway for TeraData) on Windows 32bit
Note.823534.1 How to Setup DG4Tera (Oracle Database Gateway for TeraData) on 64bit Unix
Note.437680.1How to Setup DG4Tera (Oracle Database Gateway for TeraData) Release 11 on Linux
Note.467947.1Setting up Legacy Gateways DG4ADABAS, DG4VSAM, DG4IMS)
Note.564299.1 How to Install DG4MQ on Linux

but new notes are continually being added.

The following notes have details of a configuration utility for the relevant gateway -

Note.1274157.1 Gateway Configuration Utility for Database Gateway For SQL Server
Note.1274143.1 Gateway Configuration Utility for Database Gateway for ODBC - DG4ODBC - to Connect to Non-Oracle Databases For Example - DB2, SQL*Server, Sybase, Informix, MySQL
Note.1286444.1 Gateway Configuration Utility for Database Gateway for DRDA - DG4DRDA - to Connect to DB2
Note.1286435.1 Gateway Configuration Utility for Database Gateway for Sybase

4. Troubleshooting

The following note details some of the common errors and solutions for Gateway issues -

Note.234517.1 How to Resolve Common Errors Encountered while using Transparent Gateways or Generic Connectivity

The following note details causes of some ORA-7445 errors -

Note.1420697.1 ORA-7445 Error Messages Using an Oracle Database Gateway (DG4DRDA, DG4IFMX, DG4MSQL, DG4ODBC, DG4SYBS, DG4TERA)

If you need to raise a service request with Oracle Support then the following information is needed to help speed up resolution -

- name and full version of the gateway being used
- platform and version where the gateway is installed
- version of the Oracle RDBMS being used to access the gateway
- name and full version of the non-Oracle data source being accessed
- configuration files and information -
gateway listener.ora
gateway init<sid>.ora
create database link statement
- statement causing the error
- full error being received from SQLPLUS when running the problem statement
- a gateway debug trace file from running the problem statement. This is created by adding the following to the gateway init<sid..ora file -
and running the problem statement from a new session. It is not necessary to stop and start the listener for this to take effect.
- note that for DG4DRDA 11.1 there is a different procedure for setting up debug tracing which is described in the documentation and also in these notes -
Note.221136.1 How To Trace DRDA Gateway (TG4DRDA or DG4DRDA) On Unix platforms
Note.428387.1 How To Trace The Transparent Gateway For DRDA (TG4DRDA) On Windows Platforms

Common Gateway error messages are -

ORA-28545 error diagnosed by Net8 when connecting to an agent
ORA-28500 connection from ORACLE to a non-Oracle system returned this message:
ORA-02063 preceding <str> from <name>
ORA-28511 lost RPC connection to heterogeneous remote agent using
ORA-02085 database link %s connects to %s
ORA-02062 distributed recovery received DBID <num>, expected <num >
ORA-02019 connection description for remote database not found
ORA-28513 internal error in heterogeneous remote agent
ORA-28500 connection from ORACLE to a non-Oracle system returned this message

5. Alerts

Alert notes for Gateway products are available in My Oracle Support.
To access alert notes do the following -

- logon to My Oracle Support
- choose the Knowledge tab
- In 'Knowledge Articles' click the pencil icon
- in the 'Product' option enter - gateway
- choose the gateway you want to see
- a list will be displayed if there is an alert
- there will also be a list of recently updated articles for the gateway

Who to contact for more information?

Gateway information is available from My Oracle Support (MOS) -


- Knowledge tab
- make sure you have enabled 'Browse Knowledge' in Customize
- in 'Find a Product by Name' enter 'gateway' - without the quotes
- then choose the relevant gateway
- continue in the 'What do you want to do' section

There is a My Oracle Support Database Gateways Community, a place to collaborate with peers in the industry and with Oracle experts which is live now at:


There is also an Oracle Technology Network forum available at -



News and Troubleshooting tips for Oracle Database and Enterprise Manager


« March 2015