| Event Id | 2922 |
| Source | BIPv500 |
| Description | ( BRK01.default ) The database reports that the procedure
'HR.ORADELETEPASSENGER1' in schema 'HR' has '2' overloaded versions. This is
not supported, as it cannot be determined which of the '2' definitions is
required. If the procedure 'HR.ORADELETEPASSENGER1' is not already qualified with a schema name, qualification may remove this problem. Otherwise ensure that the procedure 'HR.ORADELETEPASSENGER1' is the only procedure of this name within schema 'HR' |
| Event Information | This message from newsgroup may help you: -------------------------------------------------------------------------------- Do you have an Oracle package called 'HR' defined on your Oracle server? I'm asking because with a 2 part name the broker may confuse package and schema names. If you are using Oracle packages you should specify an explicit 3 part name, i.e. including the schema, package and procedure names. I notice that your broker and database schemas are the same ('HR') and I'm wondering if this is causing the apparent 'overload'. Have you tried putting the database stored procedure in a differently named (Oracle) schema? Another experiment would be to try allowing the database schema name to default (i.e. EXTERNAL NAME "ORADELETEPASSENGER1";) and see what, if any, procedure it locates. --------------------------------------------------------------------------------. |
| Reference Links | Event Id:2922 Source Id:BIPv500 |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.