ORA-28541: Error in HS init file on line number.

Cause : A syntax error occurred in the gateway initialization file.

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

Check gateway init file to correct the syntax error. For further information, check the error message in the gateway trace file.

update : 27-04-2017
ORA-28541

ORA-28541 - Error in HS init file on line number.
ORA-28541 - Error in HS init file on line number.

  • ora-09774 : osnmui: cannot send break message
  • ora-09838 : removeCallback: failure removing the callback port.
  • ora-31002 : Path name string is not a container
  • ora-16192 : Primary and standby network integrity mismatch
  • ora-29379 : resource plan string is involved in a loop in top-plan string
  • ora-02398 : exceeded procedure space usage
  • ora-19681 : block media recovery on control file not possible
  • ora-25103 : NOPARALLEL option can only be used with ALTER INDEX REBUILD
  • ora-19831 : incompatible string.string.string.string DBMS_BACKUP_RESTORE package: string.string.string.string required
  • ora-01589 : must use RESETLOGS or NORESETLOGS option for database open
  • ora-23618 : Generation of script string is not complete.
  • ora-29382 : validation of pending area failed
  • ora-00028 : your session has been killed
  • ora-23612 : unable to find tablespace "string"
  • ora-12477 : greatest lower bound resulted in an invalid OS label
  • ora-02064 : distributed operation not supported
  • ora-12606 : TNS: Application timeout occurred
  • ora-26099 : direct path context is already prepared
  • ora-03236 : max # extents (string) reached in index string.string subpartition string
  • ora-13380 : network not found
  • ora-28674 : cannot reference transient index-organized table
  • ora-23343 : no match for specified conflict resolution information
  • ora-00163 : internal database name length string is greater than maximum (string)
  • ora-38426 : attribute set assigned to an expression set may not be dropped
  • ora-36978 : (XSRELGID01) workspace object must be a self-relation.
  • ora-27417 : BYWEEKNO clause is only supported when FREQ=YEARLY
  • ora-02320 : failure in creating storage table for nested table column string
  • ora-00232 : snapshot control file is nonexistent, corrupt, or unreadable
  • ora-02080 : database link is in use
  • ora-02487 : Error in converting trace data
  • 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.