While trying to add a new alias for the TIBCO iProcess Web Services Plug-in via the webservices_server_location/jetty-6.1.1/urladmin utility, the following error is returned on-screen: java.sql.SQLException: ORA-01403: no data found
Article ID: KB0079770
Updated On:
| Products | Versions |
|---|---|
| TIBCO iProcess Web Services Server Plug-in | - |
Description
The following error is seen when adding a new alias via the webservices_server_location/jetty-6.1.1/urladmin utility for the TIBCO iProcess Web Services Plug-in:
java.sql.SQLException: ORA-01403: no data found
ORA-06512: at "TIBIPENG.SP_EAIWS_URL_ALIAS_SEQUENCE", line 5
ORA-06512: at line 1
This issue is due to the TIBCO iProcess Web Services Server Plug-in failing to install and update the database tables properly. This could be due to a number of reasons such as database connectivity problems, improper database permissions, etc. In this case, a select * from <table_owner>.sequences shows:
SEQ_ID SEQ_VAL SEQ_NAME
1 1709 REQID
2 909 CNUM
3 1 PROC
4 1 WAIT
5 1 CDQP_DEF
6 1 CDQP
7 1 IAP_MONITOR_ID
As seen from the above, EAIWS_URL_ALIAS and EAIWS_SECURITY_PROFILE are missing. The output should appear like:
SEQ_ID SEQ_VAL SEQ_NAME
---------- ---------- --------------------------------
1 33131 REQID
2 11031 CNUM
3 1 PROC
4 1 WAIT
5 1 CDQP_DEF
6 1 CDQP
7 1 IAP_MONITOR_ID
22 5 EAIWS_URL_ALIAS
23 6 EAIWS_SECURITY_PROFILE
Environment
Resolution
instDB2.sql
instOracle.sql
instSQLServer.sql
upgrDB2-10.6.sql
upgrOracle-10.6.sql
upgrSQLServer-10.6.sql
The appropriate script must be manually run to correct the issue. The script needing to be run depends on the database version (DB2, Oracle, or SQLServer) and whether the install was an upgrade (“upgr” prefix) or a new install (“inst” prefix). It is best to run the full (inst*.sql or upgr*.sql) script, and not parts of each script if the state of the tables is unknown and it is uncertain what tables and/or configuration was properly updated. In the instance of the error sited above the instOracle.sql was run to correct the issue since it was a new install against an Oracle database. The “table_owner” entries within the script must be properly updated to your table owner before running.
Once the script has run, confirm that the EAIWS_URL_ALIAS and EAIWS_SECURITY_PROFILE have been added to the Sequences table. Also confirm that the SP_EAIWS_URL_ALIAS_SEQUENCE appears as follows, with the exception of the schema owner which is installation dependent.
=====
SP_EAIWS_URL_ALIAS_SEQUENCE
(seq_number OUT NUMBER) AS
BEGIN
SELECT seq_val INTO seq_number FROM pro111.sequences WHERE seq_id = 22;
UPDATE pro111.sequences SET seq_val = seq_val + 1 WHERE seq_id = 22;
DBMS_OUTPUT.PUT_LINE (' SEQ_VAL');
DBMS_OUTPUT.PUT_LINE ('----------');
DBMS_OUTPUT.PUT_LINE (seq_number);
END;
=====
Issue/Introduction
Feedback
