My Oracle Support Banner

ORAPARTSEED Program Fails With "ORA-1034: ORACLE Not Available" Error When Batch Server and Database Server Are Separate Machines (Doc ID 1628259.1)

Last updated on NOVEMBER 03, 2020

Applies to:

Oracle Retail Data Warehouse - Version 13.0.5 and later
Information in this document applies to any platform.

Symptoms

User recently moved the database to an Exadata machine, resulting in a situation where the batch server and the database server are two different machines.  The ORAPARTSEED batch now fails with the below error when executed from a different server than the database server:

 

Steps to Reproduce:

  1. Run the ORAPARTSEED batch from different server than the database server.
  2. Batch fails, producing the error “Invalid Username/password”. 
  3. Also, note that appropriate error handling is not present in the program (i.e., it has been running and failing to connect via SQL*Plus, but not returning the failure code to the calling job scheduler).
  4. It was expected that the batch should be able to connect to the database on the other server. The script needs to check the return code from the SQL*Plus command.

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.