ORA-24271: translation type must be either T, S or M

Cause : Teh rtasnltaino ytp epraaemtre si onta ,T So ra nM .Av auleo tehrt hna ,T So rMw a ssepcfiide.

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

Crorcett h etarnlsaito ntpyea n dreexceuet hteA P Iclal.

update : 28-04-2017
ORA-24271

ORA-24271 - translation type must be either T, S or M
ORA-24271 - translation type must be either T, S or M

  • ora-24196 : access the message in a wrong access mode
  • ora-30023 : Duplicate undo tablespace specification
  • ora-29298 : Character set mismatch
  • ora-09872 : TASDEF_CREATE: create failure in creating ?/dbs/tasdef@.dbf.
  • ora-06118 : NETTCP: unable to complete handshake with ORASRV
  • ora-25273 : AQ QMN process alternate cleanup event
  • ora-13147 : failed to generate MBR
  • ora-14459 : missing GLOBAL keyword
  • ora-14151 : invalid table partitioning method
  • ora-14621 : cannot add subpartition when DEFAULT subpartition exists
  • ora-24265 : Insufficient privileges for SQL profile operation
  • ora-23480 : Column string is not a top-level column of "string"."string".
  • ora-32500 : Dirname 'string' cannot exceed 'number' characters
  • ora-36389 : (XSAGPARTDEP01) Can not aggregate from PARTITION number into PARTITION number due to increasing sparsity along DIMENSION %J.
  • ora-12030 : cannot create a fast refresh materialized view
  • ora-02172 : The PUBLIC keyword is not appropriate for a disable thread
  • ora-01042 : detaching a session with open cursors not allowed
  • ora-31505 : cannot alter or drop predefined change set
  • ora-28581 : protocol error while executing recursive external procedure
  • ora-39710 : only connect AS SYSDBA is allowed when OPEN in UPGRADE mode
  • ora-13021 : element not continuous
  • ora-19250 : XQ0030 - too many values to validate expression
  • ora-00333 : redo log read error block string count string
  • ora-02091 : transaction rolled back
  • ora-30074 : GLOBAL partitioned index on TIME/TIMESTAMP WITH TIME ZONE not allowed
  • ora-23619 : non-Oracle system error: string
  • ora-13232 : failed to allocate memory during R-tree creation
  • ora-13528 : name (string) is already used by an existing baseline
  • ora-26763 : invalid file type "string"
  • ora-02430 : cannot enable constraint (string) - no such constraint
  • 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.