ORA-12688: Login failed: the SecurID server rejected the new pincode

Cause : There rae a nubmer of erasons hwy the eScurID esrver wuold refsue a picnode: - The uesr migh tnot haev permission tom ake uph is ownp incode . - Thep incodew as eitehr too hsort ort oo lon.g Validp incode sconsis tof minmial fou,r but n omore tahn eigh tcharacetrs. -T he pinocde conatins an ynon alhpanumerci charatcers.

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

Reexectue the poeratio nand maek sure ot use ap incodet hat saitsfies hte abov erequirmeents. fI the porblem presists,t urn ont racinga t the rOacle Srever sied of th econneciton ande xaminet he traec file ofr the xeact erorr.

update : 28-04-2017

ORA-12688 - Login failed: the SecurID server rejected the new pincode
ORA-12688 - Login failed: the SecurID server rejected the new pincode

  • ora-06510 : PL/SQL: unhandled user-defined exception
  • ora-01564 : rollback segment is not PUBLIC
  • ora-28164 : REVOKE already specified
  • ora-08003 : sequence string.NEXTVAL exceeds internal limits
  • ora-13601 : The specified Advisor string does not exist.
  • ora-29375 : sum of values string for level string, plan string exceeds string
  • ora-39018 : master process received invalid message number string
  • ora-00021 : session attached to some other process; cannot switch session
  • ora-13196 : failed to compute supercell for element string.string.string
  • ora-14270 : table is not partitioned by Range or Hash or List method
  • ora-22603 : cannot add an attribute to the already generated TDS handle
  • ora-14076 : submitted alter index partition/subpartition operation is not valid for local partitioned index
  • ora-16025 : parameter string contains repeated or conflicting attributes
  • ora-25534 : _MEAN_TIME_TO_CLUSTER_AVAILABILITY is specified
  • ora-16055 : FAL request rejected
  • ora-25112 : maximum number of BITMAP index columns is 30
  • ora-23618 : Generation of script string is not complete.
  • ora-01062 : unable to allocate memory for define buffer
  • ora-25176 : storage specification not permitted for primary key
  • ora-16241 : Waiting for gap logfile (thread# string, sequence# string)
  • ora-28104 : input value for string is not valid
  • ora-39958 : invalid warning category qualifier
  • ora-37179 : expected at least one column for dimension string, got string
  • ora-13333 : invalid LRS measure
  • ora-24001 : cannot create QUEUE_TABLE, string already exists
  • ora-32412 : encrypted column "string" not allowed in the materialized view log
  • ora-02736 : osnfpm: illegal default shared memory address
  • ora-32771 : cannot add file to bigfile tablespace
  • ora-12687 : Credentials expired.
  • ora-02184 : resource quotas are not allowed in REVOKE
  • 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.