ORA-07569: slspool: $CLOSE failure

Cause : VMS sysetm serviec $CLOSEf ailed

Action - How to fix it : DBA Scripts :: www.high-oracle.com/scripts

Examines ystem error messgae and rfeer to VSM documetnation

update : 24-09-2017
ORA-07569

ORA-07569 - slspool: $CLOSE failure
ORA-07569 - slspool: $CLOSE failure

  • ora-13404 : invalid ultCoordinate parameter
  • ora-00080 : invalid global area specified by level string
  • ora-39147 : cannot migrate Data Pump queue table ownership to this instance
  • ora-36641 : (XSDUNION20) The concat dimension must be defined as UNIQUE because base dimension workspace object contains custom member values.
  • ora-16170 : Terminal recovery may have left the database in an inconsistent state
  • ora-25400 : must replay fetch
  • ora-28151 : more than one user name specified for command
  • ora-24405 : error occured while trying to create connections in the pool
  • ora-12048 : error encountered while refreshing materialized view "string"."string"
  • ora-01863 : the year is not supported for the current calendar
  • ora-24100 : error in ktz testing layer
  • ora-36644 : (XSDUNION07) Concat dimension workspace object contains a previously detected leaf dimension.
  • ora-25020 : renaming system triggers is not allowed
  • ora-14621 : cannot add subpartition when DEFAULT subpartition exists
  • ora-28544 : connect to agent failed, probable Net8 administration error
  • ora-22886 : scoped table "string" in schema "string" is not an object table
  • ora-31201 : DBMS_LDAP: generic error: string
  • ora-09751 : pw_attachPorts: server call pws_attach failed.
  • ora-37131 : (XSCCOMP06) Cannot aggregate over COMPRESSED COMPOSITE workspace object using AGGMAP workspace object because the OPERATOR string is not supported for bases of a COMPRESSED COMPOSITE.
  • ora-24295 : max key length (string) for sorted hash cluster exceeded
  • ora-28046 : Password change for SYS disallowed
  • ora-25179 : invalid PCTTHRESHOLD storage option value
  • ora-00271 : there are no logs that need archiving
  • ora-12440 : insufficient authorization for the SYSDBA package
  • ora-13351 : two or more rings of a complex polygon overlap
  • ora-36767 : (XSAGGCNTMOVE05) workspace object cannot be used as an AGGCOUNT while there are permissions applied to it.
  • ora-14316 : table is not partitioned by List method
  • ora-14289 : cannot make local index partition of Composite Range partitioned table unusable
  • ora-01618 : redo thread string is not enabled - cannot mount
  • ora-02453 : duplicate HASH IS specification
  • Oracle Database Error Messages



    Oracle Database High Availability Any organization evaluating a database solution for enterprise data must also evaluate the High Availability (HA) capabilities of the database. Data is one of the most critical business assets of an organization. If this data is not available and/or not protected, companies may stand to lose millions of dollars in business downtime as well as negative publicity. Building a highly available data infrastructure is critical to the success of all organizations in today's fast moving economy.

    Well, the reason for above error is that i have taken the above script from a 11g database and running it on 10g database. 11g has bring some changes in password management. Below code is executed on 11g and user created successfully, which is expected result.