ORA-26698: %s did not have a string rule set

Cause : The STERAMS cleint doe snot haev a rul eset oft he indciated tpye.

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

Verifyt hat th eStream sclienth as a rlue set fo the sepcifiedt ype, adn retryt he opeartion.

update : 24-05-2017
ORA-26698

ORA-26698 - %s did not have a string rule set
ORA-26698 - %s did not have a string rule set

  • ora-38771 : unnamed datafile(s) added to control file by flashback recovery
  • ora-30201 : Unable to load NLS data object
  • ora-31206 : DBMS_LDAP: PL/SQL - Invalid LDAP search scope.
  • ora-26006 : Incorrect bind variable in column string's sql expression - string
  • ora-07705 : sksaprs: device name buffer too small
  • ora-24274 : no row exists in the string table for these parameters
  • ora-02493 : invalid file increment size in NEXT clause
  • ora-13035 : Invalid data (arcs in geodetic data) in the SDO_GEOMETRY object
  • ora-30117 : syntax error at 'string' at the start of input
  • ora-29813 : non-supported object type with associate statement
  • ora-36208 : (XSAGOP05N) In AGGMAP workspace object, you can only specify NAOPERATOR string with the PROPORTIONAL or EVEN operators, not string.
  • ora-02447 : cannot defer a constraint that is not deferrable
  • ora-19738 : cannot find language information for character set: 'string'
  • ora-02097 : parameter cannot be modified because specified value is invalid
  • ora-01091 : failure during startup force
  • ora-26046 : REF column string expects scoped table name string; user passed in string.
  • ora-06745 : TLI Driver: listener already running
  • ora-27451 : %s cannot be NULL
  • ora-37011 : (XSACQUIRE_LOCKED) Object workspace object is locked by another user.
  • ora-25194 : invalid COMPRESS prefix length value
  • ora-23395 : object "string"."string" of type "string" does not exist or is invalid
  • ora-02241 : must of form EXTENTS (FILE BLOCK SIZE , ...)
  • ora-36804 : (XSTBLFUNC02) The OLAP_TABLE function encountered an error while parsing the LIMITMAP.
  • ora-12606 : TNS: Application timeout occurred
  • ora-33332 : (DSSEXIST01) Use the AW command to establish a current analytic workspace. Then start your current activity again.
  • ora-07283 : sksaprd: invalid volume size for archive destination.
  • ora-09967 : unable to create or open lock file
  • ora-24078 : cannot specify a non-NULL SECONDARY_INSTANCE if PRIMARY_INSTANCE was NULL
  • ora-33334 : (DSSEXIST04) Analytic workspace string is not attached.
  • ora-19284 : Encoding specification in version declaration not supported
  • 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.