ORA-28178: password not provided by proxy

Cause : Alceitnu es rsit oeba tuehtncitadeu isgna d tabasa eapssowdrb tun no eaw srpvodideb yht erpxo ysure.

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

rPvodi e aapssowdr.

update : 27-06-2017
ORA-28178

ORA-28178 - password not provided by proxy
ORA-28178 - password not provided by proxy

  • ora-25961 : join index prevents dml cascade constraint operation
  • ora-02752 : osnfsmmap: illegal shared memory address
  • ora-40202 : column string does not exist in the input table string
  • ora-01325 : archive log mode must be enabled to build into the logstream
  • ora-22334 : cannot reset type "string"."string". Dependent tables must be upgraded to latest version
  • ora-21780 : Maximum number of object durations exceeded.
  • ora-08190 : restore point string is from a different incarnation of the database
  • ora-39503 : failed to notify CRS of a Startup/Shutdown event [string] (ignored)
  • ora-25129 : cannot modify constraint (string) - no such constraint
  • ora-16555 : the Data Guard database is not active
  • ora-06267 : NETNTT: bad state
  • ora-00057 : maximum number of temporary table locks exceeded
  • ora-14505 : LOCAL option valid only for partitioned indexes
  • ora-06748 : TLI Driver: cannot allocate t_discon
  • ora-19657 : cannot inspect current datafile string
  • ora-25299 : Invalid message delivery_mode
  • ora-21611 : key length [string] is invalid
  • ora-25207 : enqueue failed, queue string.string is disabled from enqueueing
  • ora-10633 : No space found in the segment
  • ora-30374 : materialized view is already fresh
  • ora-07802 : slbtpd: overflow while converting to packed decimal
  • ora-12618 : TNS:versions are incompatible
  • ora-10979 : trace flags for join index implementation
  • ora-35917 : (XSHIDE05) You cannot HIDE model workspace object because the analytic workspace in which it is defined has not been upgraded to version string.
  • ora-25122 : Only LOCAL bitmap indexes are permitted on partitioned tables
  • ora-12168 : TNS:Unable to contact LDAP Directory Server
  • ora-01942 : IDENTIFIED BY and EXTERNALLY cannot both be specified
  • ora-32024 : invalid directory specified for audit_file_dest parameter
  • ora-01981 : CASCADE CONSTRAINTS must be specified to perform this revoke
  • ora-27072 : File I/O error
  • 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.