Links
Home
Oracle DBA Forum
Frequent Oracle Errors
TNS:could not resolve the connect identifier specified
Backtrace message unwound by exceptions
invalid identifier
PL/SQL compilation error
internal error
missing expression
table or view does not exist
end-of-file on communication channel
TNS:listener unknown in connect descriptor
insufficient privileges
PL/SQL: numeric or value error string
TNS:protocol adapter error
ORACLE not available
target host or object does not exist
invalid number
unable to allocate string bytes of shared memory
resource busy and acquire with NOWAIT specified
error occurred at recursive SQL level string
ORACLE initialization or shutdown in progress
archiver error. Connect internal only, until freed
snapshot too old
unable to extend temp segment by string in tablespace
Credential retrieval failed
missing or invalid option
invalid username/password; logon denied
unable to create INITIAL extent for segment
out of process memory when trying to allocate string bytes
shared memory realm does not exist
cannot insert NULL
TNS:unable to connect to destination
remote database not found'>ora-02019
exception encountered: core dump
inconsistent datatypes
no data found
TNS:operation timed out
PL/SQL: could not find program
existing state of packages has been discarded
maximum number of processes exceeded
error signaled in parallel query server
ORACLE instance terminated. Disconnection forced
TNS:packet writer failure
see ORA-12699
missing right parenthesis
name is already used by an existing object
cannot identify/lock data file
invalid file operation
quoted string not properly terminated
Trigger - Missing IN or OUT parameter at index: 1

Trigger - Missing IN or OUT parameter at index: 1

2004-12-06       - By Bill Coulam
Reply:     1     2     3     4     5     6  

It would help us to have the whole trigger.

It seems that you are using the trigger to prevent duplicates. Can you not
use a unique constraint for that task, trapping the
ORA-00001 (See ORA-00001.ora-code.com)/DUP_VAL_ON_INDEX exception at the application layer and displaying
a nice error message to the user?

I 'm guessing this is a BEFORE trigger since as an AFTER you 'll probably get
the ol ' mutating table problem. If it is a BEFORE trigger, the evaluation
will need to read IF (cnt >= 1), because as-is, it will only raise the error
on the third attempt, not the second.

The error number you use in RAISE_APPLICATION_ERROR needs to fall
between -20000 and -20999.

Finally, the error message you pasted here isn 't from Oracle. It is a
Java/JDBC error complaining about you 're not having set up the call to the
procedure/function properly, recount the number of IN/OUT parameters in the
PL/SQL routine you 're calling and make sure there is a matching set
statement for each. Remember that functions return a value as well.

- bill c.

-- --Original Message-- --
From: oracle-l-bounce@(protected)
[mailto:oracle-l-bounce@(protected)]On Behalf Of Lyndon Tiu
Sent: Monday, December 06, 2004 10:23 AM
To: Oracle-L
Subject: Trigger - Missing IN or OUT parameter at index: 1


Hello guys,

Could use some help here.

1) Below is a trigger body:

declare cnt number;
BEGIN
select count(*) into cnt from xdb_record_types where query_by_default =
1 and xdb_layer_type_fk = :new.xdb_layer_type_fk;
if cnt > 1 then
RAISE_APPLICATION_ERROR (
num= > -1,
msg= > 'Duplicate query by default for layer fk = ' +
:new.xdb_layer_type_fk);
end if;
END;


2) I am getting error:

"Missing IN or OUT parameter at index : 1 "


Thank you for any suggestions.

--
Lyndon Tiu
--
http://www.freelists.org/webpage/oracle-l

--
http://www.freelists.org/webpage/oracle-l