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-06-2017

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

  • ora-22290 : operation would exceed the maximum number of opened files or LOBs
  • ora-07588 : spdcr: $GETJPIW get image name failure
  • ora-32011 : cannot restore SPFILE to location already being used by the instance
  • ora-01229 : data file string is inconsistent with logs
  • ora-28113 : policy predicate has error
  • ora-37078 : (XSMCSESS06) The dimension being maintained (workspace object) cannot also be used as a step dimension.
  • ora-16579 : bad Data Guard NetSlave state detected
  • ora-25236 : buffer too small for user data
  • ora-24430 : Null values for sqltext and key were specified.
  • ora-29290 : invalid offset specified for seek
  • ora-08175 : discrete transaction restriction violated (string)
  • ora-37086 : %s is not a valueset
  • ora-38444 : statistics do not exist for the expression set
  • ora-19701 : device name exceeds maximum length of string
  • ora-14295 : column type or size mismatch between partitioning columns and subpartitioning columns
  • ora-31414 : error(s) occurred during change table advance
  • ora-29400 : data cartridge error string
  • ora-27101 : shared memory realm does not exist
  • ora-23345 : table "string"."string" not registered to collect statistics
  • ora-23443 : missing template parameter
  • ora-19578 : end of volume while duplexing to sequential files, backup piece incomplete
  • ora-32607 : invalid ITERATE value in MODEL clause
  • ora-39314 : call to DBMS_SCHEMA_COPY.SYNC_CODE is not legal
  • ora-02217 : duplicate storage option specification
  • ora-00040 : active time limit exceeded - call aborted
  • ora-07680 : sou2os: another call to Oracle currently executing
  • ora-25127 : RELY not allowed in NOT NULL constraint
  • ora-02250 : missing or invalid constraint name
  • ora-06120 : NETTCP: network driver not loaded
  • ora-32611 : incorrect use of MODEL CV operator
  • 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.