[ Pobierz całość w formacie PDF ]
.Action Assign the user to an existing profile.ORA 02381 cannot drop PUBLIC_DEFAULT profileCause An attempt was made to drop the PUBLIC_DEFAULT profile.Action The PUBLIC_DEFAULT profile cannot be dropped.ORA 02382 profile name has users assigned, cannot drop without CASCADECause An attempt was made to drop a profile that had users assigned to it withoutusing the CASCADE option of the DROP PROFILE statement.A profile thathas users assigned to it cannot be dropped, unless the CASCADE option isspecified.CASCADE reassigns users to the PUBLIC_DEFAULT profile beforedropping the profile.Action To reassign all users to the PUBLIC_DEFAULT profile, issue the DROPPROFILE statement with the CASCADE option.ORA 02383 illegal cost factorCause A negative value or UNLIMITED cost was specified for this resource in theALTER RESOURCE COST statement.Action Only positive integer values can be specified for resources in the ALTERRESOURCE COST statement.Issue the statement again, using a positiveinteger value for each resource specified.ORA 02390 exceeded COMPOSITE_LIMIT, logoff in progressCause The COMPOSITE_LIMIT for the profile is exceeded.That is, the weighted sumof the connection time, logical reads per session, CPU usage per session, andprivate SGA space used during the session exceeded the limit set by theCOMPOSITE_LIMIT clause set in the user profile.Action If this happens often, ask the database administrator to raise theCOMPOSITE_LIMIT of the user profile, or determine which resource is usedthe most and raise the limit on that resource.2 238 Oracle7 Server Messages 02376 02399: Oracle ResourcesORA 02391 exceeded simultaneous SESSIONS_PER_USER limit, maximum numCause An attempt was made to exceed the maximum number of concurrent sessionsallowed by the SESSIONS_PER_USER clause of the user profile.Action End one or more concurrent sessions or ask the database administrator toincrease the SESSIONS_PER_USER limit of the user profile.ORA 02392 exceeded session limit on CPU usage, logging offCause An attempt was made to exceed the maximum CPU usage allowed by theCPU_PER_SESSION clause of the user profile.Action If this happens often, ask the database administrator to increase theCPU_PER_SESSION limit of the user profile.ORA 02393 exceeded call limit on CPU usageCause An attempt was made to exceed the maximum CPU time for a call, a parse,execute, or fetch, allowed by the CPU_PER_CALL clause of the user profile.Action If this happens often, ask the database administrator to increase theCPU_PER_CALL limit of the user profile.ORA 02394 exceeded session limit on I/O usage, logging offCause An attempt was made to exceed the maximum I/O allowed by theLOGICAL_READS_PER_SESSION clause of the user profile.Action If this happens often, ask the database administrator to increase theLOGICAL_READS_PER_SESSION limit of the user profile.ORA 02395 exceeded call limit on I/O usageCause An attempt was made to exceed the maximum I/O for a call, a parse, execute,or fetch, allowed by the LOGICAL_READS_PER_CALL clause of theuser profile.Action If this happens often, ask the database administrator to increase theLOGICAL_READS_PER_CALL limit of the user profile.ORA 02396 exceeded max Idle Time, please connect againCause A user has exceeded the maximum time allowed to remain idle.Action The user must reconnect to the database.Oracle7 Server Messages 2 239 02376 02399: Oracle ResourcesORA 02397 exceeded PRIVATE_SGA Limit, logging offCause This error occurs only when using a multi threaded server.Action Contact the database administrator to expand the PRIVATE_SGA limit.ORA 02398 exceeded procedure space usageCause Stored procedures used up too much space in the SYSTEM tablespace.Action Use fewer stored procedures or add an additional file to the system tablespace.ORA 02399 exceeded maximum connect time, logging offCause A user has exceeded the maximum time allowed to be connected tothe database.Action The user must reconnect to the database.2 240 Oracle7 Server Messages 02400 02419: EXPLAIN PLAN Command02400 02419: EXPLAIN PLAN CommandThis sections lists messages generated when using the SQL EXPLAINPLAN command.ORA 02401 cannot EXPLAIN view owned by another userCause The view specified in the user s SQL statement belongs to another user andcannot be explained.Action Create a view that has the same definition but belongs to the current user.ORA 02402 PLAN_TABLE not foundCause The PLAN_TABLE used by EXPLAIN to describe the SQL statement does notexist in the current schema.Action Create a PLAN_TABLE in the current schema or use the INTO clause to storethe EXPLAIN results in a plan table with a different name.ORA 02403 plan table does not have correct formatCause The plan table does not have the appropriate columns.Action Redefine the plan table with the appropriate columns.ORA 02404 specified plan table not foundCause The specified plan table cannot be found.Action Create the specified plan table or use an existing one.Oracle7 Server Messages 2 241 02420 02429: Schemas02420 02429: SchemasThis section lists messages generated when commands are used that alterschemas or schema objects.ORA 02420 missing schema authorization clauseCause The schema AUTHORIZATION clause is missing in a CREATE SCHEMAstatement.Action Check the syntax of the statement, provide a valid schema AUTHORIZATIONclause, and retry the statement.ORA 02421 missing or invalid schema authorization identifierCause Either:" The schema authorization identifier is not recognized." An attempt was made to use a schema authorization identifier for a userwhile not connected as that user.Action If the cause is" an unrecognized identifier, then use an existing identifier." connected with a different user name, then disconnect and connect to thecorrect user name.ORA 02422 missing or invalid schema elementCause A statement other than a CREATE TABLE, CREATE VIEW, or GRANT appearsin a CREATE SCHEMA statement.Action See Oracle7 Server SQL Reference for the valid elements of the CREATESCHEMA statement.ORA 02423 schema name does not match schema authorization identifierCause A table definition with a schema name prepended to the table name does notmatch the schema name provided in the AUTHORIZATION clause of aCREATE SCHEMA STATEMENT.Action Check that the schema names match the one given in the CREATESCHEMA statement.2 242 Oracle7 Server Messages 02420 02429: SchemasORA 02424 potential circular view references or unknown referenced tablesCause The CREATE SCHEMA statement contains a view that depends on other viewscontained in the CREATE SCHEMA statement, or they contain references tonon existing tables.Action Create the dependent views in a separate CREATE SCHEMA statement andensure that all referenced tables are either defined in the CREATE SCHEMAstatement or exist outside the statement.ORA 02425 create table failedCause A CREATE TABLE statement failed in the CREATE SCHEMA statement.Action The cause for failure will be presented below this message.Follow theappropriate actions as suggested by the subsequent messages.ORA 02426 privilege grant failedCause A GRANT statement failed in the CREATE SCHEMA statement.Action The cause for failure will be presented below this message [ Pobierz całość w formacie PDF ]