ORA-01086: savepoint 'DBLINKTEST' never established

Hi,
Recently, I encountered the following error. I have absolutly no idea of what to do to solve it. The thing is that we have a test and production database. When I try to create my dblink on Test database, I receive the mentionned error. When I create the DBLink on production database, everything is ok.
My database is Oracle9i Enterprise Edition Release 9.2.0.8.0.
My Toad version is: 9.7.2.5.
If you need other information, don't hesitate to ask.
Thanks a lot.

[email protected] wrote:
well. After i create my dblink (with sql*plus), i try to test it with a script. The result is: ORA-03113: end-of-file communication channel. Tha's why I try to test my dblink with toad.You are looking at a different problem then. This has nothing to do with the tool which is used to create the database link in first place.
ORA-03113:     end-of-file on communication channel
Cause:      The connection between Client and Server process was broken.
Action:      There was a communication error that requires further investigation. First, check for network problems and review the SQL*Net setup. Also, look in the alert.log file for any errors. Finally, test to see whether the server process is dead and whether a trace file was generated at failure time.
So you should concentrate on resolving this error. You can refer MOS note 1020463.6 for this purpose.

Similar Messages

Savepoint RM_DISPATCH never established

I installed Designer 9.0.2 and a repository succesful, but when i try to do something in the Designer or RepositoryObjectNavigator always the same error occurs:
"Savepoint RM_DISPATCH never established"
Any hints?
Thanks

Steffen,
There are a few things you can look at:
1. If you are getting an ORA-1086, check that you have rollback segments online. You need to make sure that you have another rollback segment 'Online' other than just the SYSTEM rollback segment.
2. Check status of Designer objects:
You can do this from the RAU. Check all Privileges, and examine the Object Status for Missing, Disabled or Invalid objects. If there are any Missing objects, recreate them.
If there are any Disabled or Invalid objects, recompile them. Many times problems with objects are caused by the Oracle account not having DBMS_LOCK and DBMS_PIPE privileges. (see the installation guide)
3. Examine and/or flush your shared memory. You may need to increase the minimum shared pool size, depending on the number of users and what they are doing.
4. Examine your DB and ensure that all the objects have plenty of free extents.
Regards
Sue

ORA-55714: savepoint savepoint disabled with interleaved changes across..

We have a PL/SQL program that is called by OAF page and has savepoint logic used in it.
We are getting the below error when we call the OAF page.
***Error***
***ORA-01086: savepoint 'START_ATP' never established in this session or is invalid ORA-06512: at "APPS.XXMRPAVAIL", line 1061 ORA-55714: savepoint 'START_CALL_ATP' disabled with interleaved changes across Oracle RAC instances***
Below is the sample logic which we have written.
SAVEPOINT start_call_atp ;
MRP_ATP_PUB.Call_ATP_no_commit
(l_session_id,
l_atp_rec,
x_atp_rec ,
x_atp_supply_demand ,
x_atp_period,
x_atp_details,
x_return_status,
x_msg_data,
x_msg_count
ROLLBACK TO start_call_atp ;
Let me know for any additional information. Thanks in advance for your help.

Please find the complete code below.
PROCEDURE Call_ATP (p_sequence_id IN NUMBER
,p_requested_ship_date IN DATE
,p_mfg_source_code_list IN VARCHAR2
,p_plan_name IN VARCHAR2
,p_requested_quantity IN NUMBER DEFAULT 100000000
,p_debug_flag IN VARCHAR2 DEFAULT 'N'
,p_week_no IN NUMBER DEFAULT 0
,p_prodFamily_clause IN VARCHAR2
,p_typetabatp IN typetabatp_g
IS
-- If profile MSC: ATP Debug = Debug and Database Trace, it will only provide the Debug session file
-- So if tracing is desired, then Remove the -- from the 'ALTER SESSION ...' line below.
-- ALSO remove -- from 'ALTER SESSION ...' statement at the end of this file that turns trace off.
-- If you fail to turn off the trace then the resulting trace file cannot be analyzed properly
-- ALTER SESSION SET EVENTS = '10046 TRACE NAME CONTEXT FOREVER, LEVEL 12' ;
lv_program_name VARCHAR2(150) := gv_package_name || '.Call_ATP' ;
lv_message VARCHAR2(4000) ;
lv_resource_org_id NUMBER;
lv_resource_org_code VARCHAR(100);
l_atp_rec MRP_ATP_PUB.ATP_Rec_Typ;
p_atp_rec MRP_ATP_PUB.ATP_Rec_Typ;
x_atp_rec MRP_ATP_PUB.ATP_Rec_Typ;
x_atp_supply_demand MRP_ATP_PUB.ATP_Supply_Demand_Typ;
x_atp_period MRP_ATP_PUB.ATP_Period_Typ;
x_atp_details MRP_ATP_PUB.ATP_Details_Typ;
x_return_status VARCHAR2(2000);
x_msg_data VARCHAR2(500);
x_msg_count NUMBER;
l_session_id NUMBER;
l_error_message VARCHAR2(250);
x_error_message VARCHAR2(80);
v_file_dir VARCHAR2 (80);
i NUMBER := 0;
ln_quantity NUMBER := p_requested_quantity;
ld_request_ship_date DATE := p_requested_ship_date;
ln_instance_id NUMBER;
TYPE TypCurRef IS REF CURSOR ;
CurRef TypCurRef ;
lv_Cur VARCHAR2(32767) ;
atp_details_tab TypRecATPDetails;
atp_details_rec MRP_ATP_PUB.ATP_Rec_Typ;
lv_rep_item VARCHAR2(40);
lv_rep_item_id NUMBER;
lv_user_id NUMBER;
TYPE TypRecCur IS RECORD
(inventory_item_id NUMBER
,ItemNo VARCHAR2(30)
,source_whse_code VARCHAR2(30)
,source_organization_id NUMBER
,family VARCHAR2(150)
,demand_class VARCHAR2(30)
,family_order_by NUMBER
RecCur TypRecCur ;
ln_plan_id NUMBER ;
k NUMBER ;
s NUMBER := 0 ;
lv_prodFamily_clause VARCHAR2(32767);
BEGIN
SAVEPOINT start_ATP ;
lv_user_id := fnd_profile.value('USER_ID');
SELECT plan_id
INTO
ln_plan_id
FROM msc_plans@APS_DBLINK
WHERE compile_designator = p_plan_name ;
SELECT MAX(instance_id)
INTO
ln_instance_id
FROM apps.mrp_ap_apps_instances_all
WHERE NVL(a2m_dblink, 'APS_DBLINK') = 'APS_DBLINK';
MSC_ATP_GLOBAL.Extend_ATP(l_atp_rec, x_return_status, 1);
FOR x IN p_typetabatp.first .. p_typetabatp.last
LOOP
lv_rep_item := NULL;
lv_rep_item_id := NULL;
BEGIN
SELECT rep.rep_item,msib.inventory_item_id
INTO lv_rep_item, lv_rep_item_id
FROM xxmrp_ctp_rep_items rep,
mtl_system_items_b msib,
     org_organization_definitions ood
WHERE rep.plant_code = p_typetabatp(x).source_whse_code
AND rep.prod_family = p_typetabatp(x).Family
     AND msib.segment1 = rep.rep_item
     AND msib.organization_id = ood.organization_id
     AND ood.organization_code = rep.plant_code;
EXCEPTION
WHEN OTHERS THEN
lv_rep_item := NULL;
lv_rep_item_id := NULL;
END;
SELECT OE_ORDER_SCH_UTIL.Get_Session_Id
INTO l_session_id
FROM dual;
IF p_debug_flag <> 'N' THEN
order_sch_wb.mr_debug := 'Y' ;
order_sch_wb.file_or_terminal := 1 ;
order_sch_wb.debug_session_id := l_session_id;
FND_PROFILE.put('MSC_ATP_DEBUG', 'C');
SELECT xxau_util.getDefaultDirectory
INTO v_file_dir
FROM dual ;
order_sch_wb.file_dir := v_file_dir ;
END IF;
i := 1;
s := s + 1 ;
l_atp_rec.identifier(i) := -TO_NUMBER(TO_CHAR(p_sequence_id) || TO_CHAR(p_week_no) || TO_CHAR(s)) ;
l_atp_rec.Inventory_Item_Id(i) := nvl(lv_rep_item_id,p_typetabatp(x).Inventory_Item_Id) ;
l_atp_rec.vendor_name(i) := p_typetabatp(x).Family ;
l_atp_rec.Inventory_Item_Name(i) := NVL(lv_rep_item,p_typetabatp(x).ItemNo);
l_atp_rec.Quantity_Ordered(i) := ln_quantity;
l_atp_rec.Quantity_UOM(i) := 'Ea';
l_atp_rec.Requested_Ship_Date(i) := p_requested_ship_date;
l_atp_rec.Action(i) := 100; --ATP inquiry
l_atp_rec.Source_Organization_Id(i) := p_typetabatp(x).source_organization_id ;
l_atp_rec.OE_Flag(i) := 'N';
l_atp_rec.Insert_Flag(i) := 0;
l_atp_rec.Customer_Id(i) := null;
l_atp_rec.Customer_Site_Id(i) := null;
l_atp_rec.Calling_Module(i) := null;
l_atp_rec.Row_Id(i) := null;
l_atp_rec.Source_Organization_Code(i) := null;
l_atp_rec.Organization_Id(i) := null;
--l_atp_rec.demand_class(i)              := RecCur.demand_class;
l_atp_rec.demand_class(i) := p_typetabatp(x).demand_class;
l_error_message := null;
SAVEPOINT start_call_atp ;
MRP_ATP_PUB.Call_ATP_no_commit
(l_session_id,
l_atp_rec,
x_atp_rec ,
x_atp_supply_demand ,
x_atp_period,
x_atp_details,
x_return_status,
x_msg_data,
x_msg_count
ROLLBACK TO start_call_atp ;
IF (x_return_status = 'S') THEN
IF x_atp_rec.Inventory_item_id.count > 0 THEN
--============ Show capacity even if there is no supply/demand =======================================
FOR j IN 1..x_atp_rec.Inventory_item_id.count
LOOP
lv_resource_org_id := xxmrpavail.get_resource_org_id (x_atp_rec.Source_Organization_Id(j));
--lv_resource_org_code := xxmrpavail.get_resource_org_id (x_atp_rec.Source_Organization_Id(j));
IF SQL%ROWCOUNT = 0 THEN
IF atp_details_rec.Source_Organization_Id.count > 0 THEN
NULL;
ELSE
MSC_ATP_GLOBAL.Extend_ATP(atp_details_rec, x_return_status, 1);
END IF;
atp_details_rec.Source_Organization_Id(atp_details_rec.Source_Organization_Id.count) := x_atp_rec.Source_Organization_Id(j) ;
atp_details_rec.vendor_name(atp_details_rec.vendor_name.count) := x_atp_rec.vendor_name(j) ;
atp_details_rec.Requested_Date_Quantity(atp_details_rec.Requested_Date_Quantity.count) := x_atp_rec.Requested_Date_Quantity(j) ;
atp_details_rec.Error_Code(atp_details_rec.Error_Code.count) := x_atp_rec.Error_Code(j) ;
atp_details_rec.Inventory_Item_Name(atp_details_rec.Inventory_Item_Name.count) := x_atp_rec.Inventory_Item_Name(j) ;
END IF;
END LOOP;
IF atp_details_rec.Inventory_Item_Name.count > 0 THEN
--custom logic
END IF;
END IF;
ELSE
RAISE e_ErrATP ;
END IF; -- after calling api
l_error_message := '';
l_session_id := '' ;
x_return_status := '' ;
x_msg_data := '' ;
x_msg_count := '' ;
END LOOP; -- main loop
EXCEPTION
WHEN e_ErrATP THEN
--IF CurRef%ISOPEN THEN CLOSE CurRef ; END IF;
IF x_atp_rec.Error_Code.count > 0 AND (x_atp_rec.Error_Code(1) <> 0) THEN
SELECT meaning
INTO x_error_message
FROM mfg_lookups
WHERE lookup_type = 'MTL_DEMAND_INTERFACE_ERRORS'
AND lookup_code = x_atp_rec.Error_Code(1);
lv_message := lv_message || x_error_message ;
END IF;
xxau_util.log(lv_program_name, 'SQLERROR', lv_message, xxau_util.c_TraceLevelException) ;
raise_application_error(c_ErrATP,'ERROR: ' || lv_program_name || ': ' || lv_message) ;
WHEN OTHERS THEN
--IF CurRef%ISOPEN THEN CLOSE CurRef ; END IF;
ROLLBACK TO start_ATP;
lv_message := lv_message || substr(SQLERRM,1,4000) ;
xxau_util.log(lv_program_name, 'SQLERROR', lv_message, xxau_util.c_TraceLevelException) ;
raise_application_error(c_ErrGeneric,'ERROR: ' || lv_program_name || ': ' || lv_message) ;
END Call_ATP;

Exception SQL + ORA-01086

Hello, i have owb 9.2.0.8 install in windows 2000 server service pack 5. when i start to deploy XML file using OMBPlus oracle tool, i receive several errror follow:
# Deploiement Xml - consulter le fichier deploy_xml.log
Erreur interne : exception SQL. Contactez le support Oracle et communiquez-lui
la pile de trace ainsi que les informations n?cessaires ? la reproduction de l'erreur.
Erreur de referentiel : Exception SQL..
Nom de classe : CacheMediator. Contactez le support Oracle et communiquez-lui la pile de trace ainsi que les informations n?cessaires ? la reproduction de
l'erreur.
Nom de m?thode : executeTransactionControlStatement. Contactez le support Oracle et communiquez-lui la pile de trace ainsi que les informations
necessaires ? la reproduction de l'erreur.
Nom de methode : -1. Contactez le support Oracle et communiquez-lui la pile de
trace ainsi que les informations n?cessaires ? la reproduction de l'erreur.
Message d'erreur du r?f?rentiel : ORA-01086: le savepoint 'SP' n'a jamais etabli
. Contactez le support Oracle et communiquez-lui la pile de trace ainsi que les
informations n?cessaires ? la reproduction de l'erreur.
how i can to know the problem and how i can to resolve it ?
thank very much.

Hi,
Did you check the log file which is generated during deployement? (deploy_xml.log).
What does it say?
Regards,
Ilona

CCA-UC560-call from UC560 phones to PBX phones the call is never established.

I have a UC560 which is in a location (remote site) and I have a PBX in other location (headquarters)
The extension of UC560 phones are 3xx y the PBX extensions are 2xx.
I have a Gateway which is connected to UC560 via trunk SIP and this gateway is connected
to PBX via H.323
The UC560 was configured with CCA.
When I call from PBX phones to UC560 phones the PBX phones ring but when the call is
answered the call is finished.
When I call from UC560 phones to PBX phones the call is never established. The PBX phones
don´t ring.
Can you help me with the configuration?

Hi Paolo and Alexander,
First thanks for your help and I apologize for the delay in response because I could not answer before.
I made some changes and now the situation is as follows:
-When I call from PBX phones to UC560 phones the UC560 phones ring and sometimes when the call is answered there are RTP packets (the call is fine) but sometimes when the call is answered there is no voice (there are not RTP packets).
-When I call from UC560 phones to PBX phones the PBX phones ring but in this case there is never voice (there are not RTP packets)
I captured traffic with the Wireshark and I saw the following:
- When the call is fine from PBX Phones to UC560 Phones in the protocol H.245 is opened a logical channel between the PBX and the Gateway H.323-SIP after Terminal Capability Set (Master Slave Determination).
But when the call is not fine because there are not RTP packets I see in the protocol H.245 that no logical channel is opened after between the PBX and the Gateway H.323-SIP after Terminal Capability Set (Master Slave Determination).
Is there some parameter about protocol H.245 on Cisco gateway H.323-SIP which I can change?
If you want I can send the captured traffic.
Regards

Got Error ora-28545 when trying to establish connect sqlserver frm orcle

1) Able to configure ODBC DRIVER CONFIGURATION
2) EDITED LISTNER.ORA FILE
SID_LIST_LISTENER01 =
(SID_LIST =
(SID_DESC =
(SID_NAME= MDB)
(ORACLE_HOME = C:\app\Administrator\product\11.2.0\dbhome_4)
(PROGRAM = hsodbc)
(SID_DESC =
(SID_NAME = PLSExtProc)
(ORACLE_HOME = C:\app\Administrator\product\11.2.0\dbhome_4)
(PROGRAM = hsodbc)
LISTENER01 =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = HYRDWS4179.ES.AD.ADP.com)(PORT = 1524))
3)tnsnames.ora file
xxxxxx =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = localhost)(PORT = 1524))
(CONNECT_DATA =
(SID = MDB)
(HS = OK)
4) Status of tnsping is good
4) unable to retrive the data
ORA-28545: error diagnosed by Net8 when connecting to an agent
Unable to retrive text of network/ncr message 65535
ora-2063 preceding two lines from msd

28545 is a configuration issue -
Have a look into your listener.ora file . it lists an Oracle_home 11.2.0 but the executable you specified in the listener.ora file is hsodbc which was its name in 10g. In 11g the executable is now called dg4odbc.
So please correct your listener.ora entry:
(SID_DESC =
(SID_NAME= MDB)
(ORACLE_HOME = C:\app\Administrator\product\11.2.0\dbhome_4)
(PROGRAM = dg4odbc) #### use dg4odbc instead of hsodbc
Now STOP and START the listener using lsnrctl command (lsnrctl stop listener01 - lsnrctl start listener01)
When it continues to fail, please provide me the output of the listener status listener01 command, the tnsping command output and which windows version (including the word size -32/64bit) and Oracle dg4odbc release you are trying to use.

I've been trying to create a Skype account, but I can never establish a secure connection to website

No matter which browser I use (Safari, Firefox or Chrome), I can't get to the page to create a new account / sign into an account because the browser can't establish a secure connection. For example, Safari gives me this message: Safari can't open the page "https://secure.skype.com/portal/overview" because Safari can't establish a secure connection to the server "secure.skype.com". Firefox and Chrome give me similar messages. I downloaded the application to my MacBook Pro without any issue, so I really don't understand why this seemingly simple step is giving me trouble.

We are currently experiencing issues with several Skype services including account registration. Our engineers are investigating the issue and hope to resolve soon. We apologize for the inconvenience. Follow further updates here: http://heartbeat.skype.com/2015/07/skype_web-service_disruption.html

I tried to purchase an app from another computer and it asked for security questions that I never established

It asked for answers that I did institute , how do I edit this ?

The Apple Support Communities are an international user to user technical support forum. As a man from Mexico, Spanish is my native tongue. I do not speak English very well, however, I do write in English with the aid of the Mac OS X spelling and grammar checks. I also live in a culture perhaps very very different from your own. When offering advice in the ASC, my comments are not meant to be anything more than helpful and certainly not to be taken as insults.
There isn't much that can be done at this point. If you did not set up the questions then I would be concerned that someone else has taken over your account. If there is a bank card in the account I would alert your bank.

How can I get a list of active savepoints for the current session?

Hi,
In Oracle Applications, we are getting the following error while performing ROLLBACK to a Savepoint.
"Unexpected Error: ORA-01086: savepoint 'PTNR_BULK_CALC_TAX_PVT' never establishe d ORA-06510: PL/SQL: unhandled user-defined exception"
So how can I get a list of active savepoints for the current session?
Could you please also let me know if there is any better way to debug this issue.
Appreciate any quick response as the issue is very critical.
Thanks,
Soma

user776523 wrote:
Hi,
In Oracle Applications, we are getting the following error while performing ROLLBACK to a Savepoint.
"Unexpected Error: ORA-01086: savepoint 'PTNR_BULK_CALC_TAX_PVT' never establishe d ORA-06510: PL/SQL: unhandled user-defined exception"It sounds like there's an execution path in the code where the SAVEPOINT is never issued.
There is no way to get a list of active savepoints. Is this your code or a "canned" procedure? If it is your code you can go through the code looking for answers, possibly tracing execution using DBMS_OUTPUT.PUT_LINE or writing messages to a log table. If its a "canned" procedure you may need to open an SR with Oracle

Savepoint issue

create table test (num NUMBER);
insert into test values(1);
insert into test values(9);
savepoint a;
insert into test values(7);
update test set num=100 where num=9;
savepoint b;
delete from test where num=1;
commit;
delete from test where num=1;I am getting an error when i issue
rollback to savepoint a;
error
SQL Error: ORA-01086: savepoint 'A' never established
01086. 00000 - "savepoint '%s' never established"
CORRECTED THE ERROR CODE
Edited by: Rahul India on Feb 19, 2013 2:39 PM

Hi,
See below which I executed in my database (11.2)
You are getting the error because you are using ROLLBACK TO <Savepoint_Name> after executing the COMMIT. After commiting savepoints which were created previously will not exist.
SQL> create table test (num NUMBER);
Table created
SQL> insert into test values(1);
1 row inserted
SQL> insert into test values(9);
1 row inserted
SQL> savepoint a;
Savepoint created
SQL> insert into test values(7);
1 row inserted
SQL> update test set num=100 where num=9;
1 row updated
SQL> savepoint b;
Savepoint created
SQL> delete from test where num=1;
1 row deleted
SQL> commit;
Commit complete
SQL> delete from test where num=1;
0 rows deleted
SQL> rollback to savepoint a;
rollback to savepoint a
ORA-01086: savepoint 'A' never established in this session or is invalid
SQL> If I remove COMMIT then SAVEPOINT will exist
SQL> insert into test values(1);
1 row inserted
SQL> insert into test values(9);
1 row inserted
SQL>   savepoint a;
Savepoint created
SQL> insert into test values(7);
1 row inserted
SQL>   update test set num=100 where num=9;
1 row updated
SQL>   savepoint b;
Savepoint created
SQL> delete from test where num=1;
1 row deleted
SQL> delete from test where num=1;
0 rows deleted
SQL> rollback to savepoint a;
Rollback complete
SQL> Edited by: Suri on Feb 19, 2013 2:40 PM

OracleXMLSave - savepoint?

How do I fix this error?
oracle.xml.sql.OracleXMLSQLException: ORA-01086: savepoint 'SYS_XSU_HOPE_0001000' never established
at oracle.xml.sql.dml.OracleXMLSave.saveXML(OracleXMLSave.java:1967)
at oracle.xml.sql.dml.OracleXMLSave.saveXML(OracleXMLSave.java:1880)
at oracle.xml.sql.dml.OracleXMLSave.insertXML(OracleXMLSave.java:1013)
at test.main(test.java:563)

I found out that this error was caused because there were existing data on the target tables. So, this error fixed.
Anyway, Yes, I'm using the latest version of XDK and XSU.
But, I have another error which I posted before.
Here is copy of that msg.
I get an error when I try to insert a huge XML file (30MB) into Oracle DB using Oracle XML Utility for Java.
Here is a segment of my Java code :
OracleXMLSave save = new OracleXMLSave(conn, tableName);
url = new URL("file:///" + xmlFile.getAbsolutePath());
rowCount = save.insertXML(url);
save.close();
Here is error msg :
# An unexpected exception has been detected in native code outside the VM.
# Program counter=0x404b44a7
# Problematic Thread: prio=1 tid=0x804ede0 nid=0x66c5 runnable
# # An unexpected exception has been detected in native code outside the VM.# Program counter=0x404741a3
# Problematic Thread: prio=1078150424 tid=0x804ede0 nid=0x66c5 runnable
Aborted
I'm not sure if there is a limit of XML file size for doing this.
It works well when XML file size is smaller.(less than 10MB)
null

Page and Tab create error

I am getting PAGE_CREATE error while adding a new page. On create new page, after filling page name & description it displays the error message below.
I am runing iAS9\Portal 3.0.8.9 on Win NT4.
No installation errors.
Exact error message:
=======================
ORA-01086: savepoint 'PAGE_CREATE' never established
ORA-06512: at "PORTAL30.WWPOB_PAGE_EDIT", line 320
ORA-06510: PL/SQL: unhandled user-defined exception
ORA-06512: at "PORTAL30.WWPOB_API_PAGE", line 340
ORA-06510: PL/SQL: unhandled user-defined exception
ORA-01400: cannot insert NULL into ("PORTAL30"."WWPOB_PORTLET_INSTANCE$"."PROVIDER_ID")
ORA-06512: at line 8
=======================
Recompiled all packages\package body (there are no 'Invalid' packages) - error still persist.
when this error occurs, portal displays error message on adding a tab (it happens when I click on the tab icon to add a new tab):
Exact error message:
=======================
Portlet Information could not be obtained. (WWC-44334)
An unexpected error occurred: ORA-06550: line 1, column 34:
PLS-00103: Encountered the symbol "." when expecting one of the following:
( - + mod not null <an identifier>
<a double-quoted delimited-identifier> <a bind variable> avg
count current exists max min prior sql stddev sum variance
execute forall time timestamp interval date
<a string literal with character set specification>
<a number> <a single-quoted SQL string>
The symbol "." was ignored. (WWC-43000)
=======================
Everything else in Portal is working fine.
All Rollbacks are online, no error message in the DB alert log.
Any suggestions on how to fix this (other than re-installing portal).
Thanks.
null

Well ... this appears to be a serious problem with the Portal as it renders it incapable of adding pages and tabs. I've tried reinstalling it on 3 different servers, used another instance of Oracle database, and the result is still the same. No installation errors, and suddenly after 7-10 days this error starts appearing.
Am I the only one experiencing this type of error? ...and can anyone offer\suggest ways to fix it?

Error when creating Final Accounting Post to GL in AR

Hello,
I currently getting an error while creating Final Accounting Post to GL
I have changed the Profile Option SLA: Enable Trace to <null> as mentioned in the solution on metalink. But still I'm getting this error.
If anyone has encountered the error(LOG) below; please reply me as soon as possible
thanks
mevin
THE LOG
Subledger Accounting: Version : 12.0.0
Copyright (c) 1979, 1999, Oracle Corporation. All rights reserved.
XLAACCPB module: Create Accounting
Current system time is 14-AUG-2009 09:36:54
XDO Data Engine Version No: 5.6.3
Resp: 50832
Org ID : 102
Request ID: 499751
All Parameters: P_APPLICATION_ID=222:P_SOURCE_APPLICATION_ID=:P_DUMMY=:P_LEDGER_ID=2089:P_PROCESS_CATEGORY_CODE=:P_END_DATE=:P_CREATE_ACCOUNTING_FLAG=N:P_DUMMY_PARAM_1=:P_ACCOUNTING_MODE=:P_DUMMY_PARAM_2=:P_ERRORS_ONLY_FLAG=N:P_REPORT_STYLE=D:P_TRANSFER_TO_GL_FLAG=Y:P_DUMMY_PARAM_3=:P_POST_IN_GL_FLAG=Y:P_GL_BATCH_NAME=:P_MIN_PRECISION=2:P_INCLUDE_ZERO_AMOUNT_LINES=:P_REQUEST_ID=:P_ENTITY_ID=118514:P_SOURCE_APPLICATION_NAME=:P_APPLICATION_NAME=:P_LEDGER_NAME=:P_PROCESS_CATEGORY_NAME=:P_CREATE_ACCOUNTING=:P_ACCOUNTING_MODE_NAME=:P_ERRORS_ONLY=:P_ACCOUNTING_REPORT_LEVEL=:P_TRANSFER_TO_GL=:P_POST_IN_GL=:P_INCLUDE_ZERO_AMT_LINES=:P_VALUATION_METHOD_CODE=:P_SECURITY_INT_1=:P_SECURITY_INT_2=:P_SECURITY_INT_3=:P_SECURITY_CHAR_1=:P_SECURITY_CHAR_2=:P_SECURITY_CHAR_3=:P_CONC_REQUEST_ID=:P_INCLUDE_USER_TRX_ID_FLAG=:P_INCLUDE_USER_TRX_IDENTIFIERS=:P_USER_ID=:DebugFlag=
Data Template Code: XLAACCPB
Data Template Application Short Name: XLA
Debug Flag:
{P_ACCOUNTING_REPORT_LEVEL=, P_DUMMY=, P_ACCOUNTING_MODE_NAME=, P_ERRORS_ONLY_FLAG=N, P_REPORT_STYLE=D, P_GL_BATCH_NAME=, P_END_DATE=, P_SECURITY_INT_3=, P_SECURITY_INT_2=, P_SECURITY_INT_1=, P_VALUATION_METHOD_CODE=, P_POST_IN_GL=, P_TRANSFER_TO_GL=, P_TRANSFER_TO_GL_FLAG=Y, P_INCLUDE_USER_TRX_IDENTIFIERS=, P_USER_ID=, P_PROCESS_CATEGORY_NAME=, P_ERRORS_ONLY=, P_DUMMY_PARAM_3=, P_SECURITY_CHAR_3=, P_DUMMY_PARAM_2=, P_SECURITY_CHAR_2=, P_DUMMY_PARAM_1=, P_SECURITY_CHAR_1=, P_ENTITY_ID=118514, P_PROCESS_CATEGORY_CODE=, P_INCLUDE_ZERO_AMT_LINES=, P_LEDGER_ID=2089, P_POST_IN_GL_FLAG=Y, P_APPLICATION_ID=222, P_INCLUDE_USER_TRX_ID_FLAG=, P_APPLICATION_NAME=, P_REQUEST_ID=, P_CONC_REQUEST_ID=, P_LEDGER_NAME=, P_SOURCE_APPLICATION_ID=, P_CREATE_ACCOUNTING=, P_CREATE_ACCOUNTING_FLAG=N, P_MIN_PRECISION=2, P_SOURCE_APPLICATION_NAME=, P_INCLUDE_ZERO_AMOUNT_LINES=, P_ACCOUNTING_MODE=}
Calling XDO Data Engine...
[081409_093744202][][EXCEPTION] SQLException encounter while executing data trigger....
java.sql.SQLException: ORA-20001: -: XLA-95103: An internal error occurred. Please inform your system administrator or support representative that:
An internal error has occurred in the program xla_create_acct_rpt_pvt.BeforeReport . ORA-20001: -: XLA-95103: An internal error occurred. Please inform your system administrator or support representative that:
An internal error has occurred in the program xla_accounting_pkg.accounting_program_document. ORA-01086: savepoint 'SP_EVENTS' never established
ORA-20001: -: XLA-95103: An internal
ORA-06512: at "APPS.APP_EXCEPTION", line 72
ORA-06512: at "APPS.XLA_EXCEPTIONS_PKG", line 110
ORA-06512: at "APPS.XLA_EXCEPTIONS_PKG", line 289
ORA-06512: at "APPS.XLA_EXCEPTIONS_PKG", line 162
ORA-06512: at "APPS.XLA_CREATE_ACCT_RPT_PVT", line 262
ORA-06512: at line 4
     at java.lang.Throwable.<init>(Throwable.java:57)
     at java.lang.Throwable.<init>(Throwable.java:68)
     at java.sql.SQLException.<init>(SQLException.java:55)
     at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)
     at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:331)
     at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:288)
     at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:745)
     at oracle.jdbc.driver.T4CCallableStatement.doOall8(T4CCallableStatement.java:215)
     at oracle.jdbc.driver.T4CCallableStatement.executeForRows(T4CCallableStatement.java:965)
     at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1170)
     at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3339)
     at oracle.jdbc.driver.OraclePreparedStatement.execute(OraclePreparedStatement.java:3445)
     at oracle.jdbc.driver.OracleCallableStatement.execute(OracleCallableStatement.java:4394)
     at oracle.apps.xdo.dataengine.XMLPGEN.executeTriggers(XMLPGEN.java:699)
     at oracle.apps.xdo.dataengine.XMLPGEN.processData(XMLPGEN.java:255)
     at oracle.apps.xdo.dataengine.XMLPGEN.processXML(XMLPGEN.java:205)
     at oracle.apps.xdo.dataengine.XMLPGEN.writeXML(XMLPGEN.java:237)
     at oracle.apps.xdo.dataengine.DataProcessor.processData(DataProcessor.java:364)
     at oracle.apps.xdo.oa.util.DataTemplate.processData(DataTemplate.java:236)
     at oracle.apps.xdo.oa.cp.JCP4XDODataEngine.runProgram(JCP4XDODataEngine.java:293)
     at oracle.apps.fnd.cp.request.Run.main(Run.java:157)
Start of log messages from FND_FILE
14-AUG-2009 09:37:19 - Beginning of the Report
GL Inerface tablename = GL_INTERFACE
GL Inerface tablename = GL_INTERFACE
tablename = GL_INTERFACE
14-AUG-2009 09:37:19- Submitting the Journal Import
GL Inerface tablename = GL_INTERFACE
GL Inerface tablename = GL_INTERFACE
tablename = GL_INTERFACE
14-AUG-2009 09:37:19- Submitting the Journal Import
14-AUG-2009 09:37:44- Journal Import completed
ORA-20001: -: XLA-95103: An internal error occurred. Please inform your system administrator or support representative that:
An internal error has occurred in the program xla_create_acct_rpt_pvt.BeforeReport . ORA-20001: -: XLA-95103: An internal error occurred. Please inform your system administrator or support representative that:
An internal error has occurred in the program xla_accounting_pkg.accounting_program_document. ORA-01086: savepoint 'SP_EVENTS' never established
ORA-20001: -: XLA-95103: An internal
ORA-06512: at "APPS.APP_EXCEPTION", line 72
ORA-06512: at "APPS.XLA_EXCEPTIONS_PKG", line 110
ORA-06512: at "APPS.XLA_EXCEPTIONS_PKG", line 289
ORA-06512: at "APPS.XLA_EXCEPTIONS_PKG", line 162
ORA-06512: at "APPS.XLA_CREATE_ACCT_RPT_PVT", line 262
ORA-06512: at line 4
End of log messages from FND_FILE
Executing request completion options...
Finished executing request completion options.
Concurrent request completed
Current system time is 14-AUG-2009 09:37:45
---------------------------------------------------------------------------

select * from gl_je_sources_tl;
main columns to look at are:
IMPORT_USING_KEY_FLAG
je_source_name
je_source_key
user_je_source_name
select * from gl_je_categories;
main columns to look at are:
je_category_key
user_je_category_name
If import_using_key_flag is Y for your je_source (Receivables), for the application (222) you are running Create Accounting in Final Post Mode, then apply the patch 8568620
By
Vamsi

Error while working with OracleApps Adapter please help mee

<bindingFault xmlns="http://schemas.oracle.com/bpel/extension"><part name="code"><code>1086</code>
</part><part name="summary"><summary>file:/F:/product/10.1.3.1/OracleAS_2/bpel/domains/test/tmp/.bpel_RepairOrder_1.0_4bac0e828ef344d37656722b167615db.tmp/CreateRepairOrder.wsdl [ CreateRepairOrder_ptt::CreateRepairOrder(InputParameters,OutputParameters) ] - WSIF JCA Execute of operation 'CreateRepairOrder' failed due to: Error while trying to prepare and execute an API.
An error occurred while preparing and executing the APPS.XX_BPEL_CREATEREPAIRORDER.CSD_REPAIRS_PUB$CREATE_REPAIR API. Cause: java.sql.SQLException: ORA-01086: savepoint 'CREATE_REPAIR_ORDER_PUB' never established
ORA-06512: at "APPS.JTF_PLSQL_API", line 65
ORA-06512: at "APPS.CSD_REPAIRS_PUB", line 144
ORA-06510: PL/SQL: unhandled user-defined exception
ORA-06512: at "APPS.XX_BPEL_CREATEREPAIRORDER", line 160
ORA-06512: at line 1
[Caused by: ORA-01086: savepoint 'CREATE_REPAIR_ORDER_PUB' never established
ORA-06512: at "APPS.JTF_PLSQL_API", line 65
ORA-06512: at "APPS.CSD_REPAIRS_PUB", line 144
ORA-06510: PL/SQL: unhandled user-defined exception
ORA-06512: at "APPS.XX_BPEL_CREATEREPAIRORDER", line 160
ORA-06512: at line 1
; nested exception is:
     ORABPEL-11811
Error while trying to prepare and execute an API.
An error occurred while preparing and executing the APPS.XX_BPEL_CREATEREPAIRORDER.CSD_REPAIRS_PUB$CREATE_REPAIR API. Cause: java.sql.SQLException: ORA-01086: savepoint 'CREATE_REPAIR_ORDER_PUB' never established
ORA-06512: at "APPS.JTF_PLSQL_API", line 65
ORA-06512: at "APPS.CSD_REPAIRS_PUB", line 144
ORA-06510: PL/SQL: unhandled user-defined exception
ORA-06512: at "APPS.XX_BPEL_CREATEREPAIRORDER", line 160
ORA-06512: at line 1
[Caused by: ORA-01086: savepoint 'CREATE_REPAIR_ORDER_PUB' never established
ORA-06512: at "APPS.JTF_PLSQL_API", line 65
ORA-06512: at "APPS.CSD_REPAIRS_PUB", line 144
ORA-06510: PL/SQL: unhandled user-defined exception
ORA-06512: at "APPS.XX_BPEL_CREATEREPAIRORDER", line 160
ORA-06512: at line 1
Check to ensure that the API is defined in the database and that the parameters match the signature of the API. Contact oracle support if error is not fixable.
</summary>
</part><part name="detail"><detail>
Internal Exception: java.sql.SQLException: ORA-01086: savepoint 'CREATE_REPAIR_ORDER_PUB' never established
ORA-06512: at "APPS.JTF_PLSQL_API", line 65
ORA-06512: at "APPS.CSD_REPAIRS_PUB", line 144
ORA-06510: PL/SQL: unhandled user-defined exception
ORA-06512: at "APPS.XX_BPEL_CREATEREPAIRORDER", line 160
ORA-06512: at line 1
Error Code: 1086</detail>
</part></bindingFault>

create or replace
PACKAGE BODY CSD_REPAIRS_PUB as
/* $Header: csdpdrab.pls 120.12 2006/09/05 11:57:18 vparvath noship $ */
* This is the public interface for the Depot Repair API. It allows
* execution of various Depot Repair APIs.
* @rep:scope public
* @rep:product CSD
* @rep:displayname Depot Repair APIs
* @rep:lifecycle active
* @rep:category BUSINESS_ENTITY CSD_REPAIR_ORDER
-- Package name : CSD_REPAIRS_PUB
-- Purpose : This package contains the public APIs for creating
-- and updating repair orders.
-- History :
-- Version Date Name Description
-- 115.0 11/17/99 pkdas Created.
-- 115.1 12/18/99 pkdas
-- 115.2 01/04/00 pkdas
-- 115.3 02/09/00 pkdas Added p_REPAIR_LINE_ID as IN parameter in the
-- Create_Repairs procedure.
-- Added p_REPAIR_NUMBER as OUT parameter in the
-- Create_Repairs procedure.
-- 115.4 02/29/00 pkdas Changed the procedure name
-- Create_Repairs -> Create_Repair_Order
-- Update_Repairs -> Update_Repair_Order
-- Added p_validation_level to Create_Repair_Order and
-- Update_Repair_Order
-- NOTE :
G_PKG_NAME CONSTANT VARCHAR2(30) := 'CSD_REPAIRS_PUB';
G_FILE_NAME CONSTANT VARCHAR2(12) := 'csdpdrab.pls';
g_debug NUMBER := csd_gen_utility_pvt.g_debug_level;
* Create Repair Order
* @param P_Api_Version_Number api version number
* @param P_Init_Msg_List initial the message stack, default to false
* @param P_Commit to decide whether to commit the transaction or not, default to false
* @param p_validation_level validation level, default to full level
* @param p_repair_line_id repair line id is unique id
* @param P_REPLN_Rec repiar line record
* @param p_create_default_logistics flag to create logistics lines, default to N
* @param X_REPAIR_LINE_ID repair line id of the created repair order
* @param X_REPAIR_NUMBER repair number of the created repair order which display on Depot UI
* @param X_Return_Status return status
* @param X_Msg_Count return message count
* @param X_Msg_Data return message data
* @rep:scope public
* @rep:lifecycle active
* @rep:displayname Create Repair Order
PROCEDURE Create_Repair_Order(P_Api_Version_Number IN NUMBER,
P_Init_Msg_List IN VARCHAR2 := FND_API.G_FALSE,
P_Commit IN VARCHAR2 := FND_API.G_FALSE,
p_validation_level IN NUMBER := FND_API.G_VALID_LEVEL_FULL,
P_REPAIR_LINE_ID IN NUMBER := FND_API.G_MISS_NUM,
P_REPLN_Rec IN CSD_REPAIRS_PUB.REPLN_Rec_Type,
p_create_default_logistics IN VARCHAR2 := 'N',
X_REPAIR_LINE_ID OUT NOCOPY NUMBER,
X_REPAIR_NUMBER OUT NOCOPY VARCHAR2,
X_Return_Status OUT NOCOPY VARCHAR2,
X_Msg_Count OUT NOCOPY NUMBER,
X_Msg_Data OUT NOCOPY VARCHAR2) IS
l_api_name CONSTANT VARCHAR2(30) := 'Create_Repair_Order';
l_api_version_number CONSTANT NUMBER := 1.0;
BEGIN
-- Standard Start of API savepoint
SAVEPOINT CREATE_REPAIR_ORDER_PUB;
-- Standard call to check for call compatibility.
IF NOT FND_API.Compatible_API_Call(l_api_version_number,
p_api_version_number,
l_api_name,
G_PKG_NAME)
THEN
RAISE FND_API.G_EXC_UNEXPECTED_ERROR;
END IF;
-- Initialize message list if p_init_msg_list is set to TRUE.
IF FND_API.to_Boolean(p_init_msg_list)
THEN
FND_MSG_PUB.initialize;
END IF;
-- Initialize API return status to success
x_return_status := FND_API.G_RET_STS_SUCCESS;
-- API body
CSD_REPAIRS_PVT.Create_Repair_Order(P_Api_Version_Number => 1.0,
P_Init_Msg_List => p_init_msg_list,
P_Commit => p_commit,
P_Validation_Level => p_validation_level,
P_REPAIR_LINE_ID => p_REPAIR_LINE_ID,
P_REPLN_Rec => p_REPLN_Rec,
X_REPAIR_LINE_ID => x_REPAIR_LINE_ID,
X_REPAIR_NUMBER => x_REPAIR_NUMBER,
X_Return_Status => x_return_status,
X_Msg_Count => x_msg_count,
X_Msg_Data => x_msg_data);
-- Check return status from the above procedure call
IF not (x_return_status = FND_API.G_RET_STS_SUCCESS)
then
ROLLBACK TO CREATE_REPAIR_ORDER_PUB;
return;
END IF;
IF (P_CREATE_DEFAULT_LOGISTICS = 'Y') THEN
CSD_LOGISTICS_PVT.Create_Default_Logistics
( p_api_version => P_Api_Version_Number,
p_commit => P_Commit,
p_init_msg_list => P_Init_Msg_List,
p_validation_level => p_validation_level,
p_repair_line_id => P_REPAIR_LINE_ID,
x_return_status => X_Return_Status,
x_msg_count => X_Msg_Count,
x_msg_data => X_Msg_Data
IF NOT(x_return_status = FND_API.G_RET_STS_SUCCESS) THEN
RAISE FND_API.G_EXC_ERROR;
END IF;
END IF;
-- End of API body.
-- Standard check for p_commit
IF FND_API.to_Boolean(p_commit)
THEN
COMMIT WORK;
END IF;
-- Standard call to get message count and if count is 1, get message info.
FND_MSG_PUB.Count_And_Get(p_count => x_msg_count,
p_data => x_msg_data);
EXCEPTION
WHEN FND_API.G_EXC_ERROR THEN
JTF_PLSQL_API.HANDLE_EXCEPTIONS(P_API_NAME => L_API_NAME,-------------------------------line 144 error
P_PKG_NAME => G_PKG_NAME,
P_EXCEPTION_LEVEL => FND_MSG_PUB.G_MSG_LVL_ERROR,
P_PACKAGE_TYPE => JTF_PLSQL_API.G_PUB,
X_MSG_COUNT => X_MSG_COUNT,
X_MSG_DATA => X_MSG_DATA,
X_RETURN_STATUS => X_RETURN_STATUS);
-- RAISE;
WHEN FND_API.G_EXC_UNEXPECTED_ERROR THEN
JTF_PLSQL_API.HANDLE_EXCEPTIONS(P_API_NAME => L_API_NAME,
P_PKG_NAME => G_PKG_NAME,
P_EXCEPTION_LEVEL => FND_MSG_PUB.G_MSG_LVL_UNEXP_ERROR,
P_PACKAGE_TYPE => JTF_PLSQL_API.G_PUB,
X_MSG_COUNT => X_MSG_COUNT,
X_MSG_DATA => X_MSG_DATA,
X_RETURN_STATUS => X_RETURN_STATUS);
-- RAISE;
WHEN OTHERS THEN
JTF_PLSQL_API.HANDLE_EXCEPTIONS(P_API_NAME => L_API_NAME,
P_PKG_NAME => G_PKG_NAME,
P_EXCEPTION_LEVEL => JTF_PLSQL_API.G_EXC_OTHERS,
P_PACKAGE_TYPE => JTF_PLSQL_API.G_PUB,
X_MSG_COUNT => X_MSG_COUNT,
X_MSG_DATA => X_MSG_DATA,
X_RETURN_STATUS => X_RETURN_STATUS);
-- RAISE;
End Create_Repair_Order;
PROCEDURE Update_Repair_Order(P_Api_Version_Number IN NUMBER,
P_Init_Msg_List IN VARCHAR2 := FND_API.G_FALSE,
P_Commit IN VARCHAR2 := FND_API.G_FALSE,
p_validation_level IN NUMBER := FND_API.G_VALID_LEVEL_FULL,
p_REPAIR_LINE_ID IN NUMBER,
P_REPLN_Rec IN OUT NOCOPY CSD_REPAIRS_PUB.REPLN_Rec_Type,
X_Return_Status OUT NOCOPY VARCHAR2,
X_Msg_Count OUT NOCOPY NUMBER,
X_Msg_Data OUT NOCOPY VARCHAR2) IS
l_api_name CONSTANT VARCHAR2(30) := 'Update_Repair_Order';
l_api_version_number CONSTANT NUMBER := 1.0;
BEGIN
-- Standard Start of API savepoint
SAVEPOINT UPDATE_REPAIR_ORDER_PUB;
-- Standard call to check for call compatibility.
IF NOT FND_API.Compatible_API_Call(l_api_version_number,
p_api_version_number,
l_api_name,
G_PKG_NAME)
THEN
RAISE FND_API.G_EXC_UNEXPECTED_ERROR;
END IF;
-- Initialize message list if p_init_msg_list is set to TRUE.
IF FND_API.to_Boolean(p_init_msg_list)
THEN
FND_MSG_PUB.initialize;
END IF;
-- Initialize API return status to SUCCESS
x_return_status := FND_API.G_RET_STS_SUCCESS;
-- API body
CSD_repairs_PVT.Update_Repair_Order(P_Api_Version_Number => 1.0,
P_Init_Msg_List => p_init_msg_list,
P_Commit => p_commit,
P_Validation_Level => p_validation_level,
p_REPAIR_LINE_ID => p_repair_line_id,
P_REPLN_Rec => p_REPLN_Rec,
X_Return_Status => x_return_status,
X_Msg_Count => x_msg_count,
X_Msg_Data => x_msg_data);
-- Check return status from the above procedure call
IF not (x_return_status = FND_API.G_RET_STS_SUCCESS)
then
ROLLBACK TO UPDATE_REPAIR_ORDER_PUB;
return;
END IF;
-- End of API body.
-- Standard check for p_commit
IF FND_API.to_Boolean(p_commit)
THEN
COMMIT WORK;
END IF;
-- Standard call to get message count and if count is 1, get message info.
FND_MSG_PUB.Count_And_Get(p_count => x_msg_count,
p_data => x_msg_data);
EXCEPTION
WHEN FND_API.G_EXC_ERROR THEN
JTF_PLSQL_API.HANDLE_EXCEPTIONS(P_API_NAME => L_API_NAME,
P_PKG_NAME => G_PKG_NAME,
P_EXCEPTION_LEVEL => FND_MSG_PUB.G_MSG_LVL_ERROR,
P_PACKAGE_TYPE => JTF_PLSQL_API.G_PUB,
X_MSG_COUNT => X_MSG_COUNT,
X_MSG_DATA => X_MSG_DATA,
X_RETURN_STATUS => X_RETURN_STATUS);
-- RAISE;
WHEN FND_API.G_EXC_UNEXPECTED_ERROR THEN
JTF_PLSQL_API.HANDLE_EXCEPTIONS(P_API_NAME => L_API_NAME,
P_PKG_NAME => G_PKG_NAME,
P_EXCEPTION_LEVEL => FND_MSG_PUB.G_MSG_LVL_UNEXP_ERROR,
P_PACKAGE_TYPE => JTF_PLSQL_API.G_PUB,
X_MSG_COUNT => X_MSG_COUNT,
X_MSG_DATA => X_MSG_DATA,
X_RETURN_STATUS => X_RETURN_STATUS);
-- RAISE;
WHEN OTHERS THEN
JTF_PLSQL_API.HANDLE_EXCEPTIONS(P_API_NAME => L_API_NAME,
P_PKG_NAME => G_PKG_NAME,
P_EXCEPTION_LEVEL => JTF_PLSQL_API.G_EXC_OTHERS,
P_PACKAGE_TYPE => JTF_PLSQL_API.G_PUB,
X_MSG_COUNT => X_MSG_COUNT,
X_MSG_DATA => X_MSG_DATA,
X_RETURN_STATUS => X_RETURN_STATUS);
-- RAISE;
End Update_Repair_Order;
-- R12 Development Begin
* Update Repair Order Status
* @param P_Api_Version api version number
* @param P_Commit to decide whether to commit the transaction or not, default to false
* @param P_Init_Msg_List initial the message stack, default to false
* @param X_Return_Status return status
* @param X_Msg_Count return message count
* @param X_Msg_Data return message data
* @param P_Repair_status_rec repair status attributes record.
* @param P_status_upd_control_rec repair status record control flags.
* @param X_OBJECT_VERSION_NUMBER
* @rep:scope public
* @rep:lifecycle active
* @rep:displayname Update Repair Order Status
PROCEDURE Update_Ro_Status(P_Api_Version IN NUMBER,
P_Commit IN VARCHAR2,
P_Init_Msg_List IN VARCHAR2,
X_Return_Status OUT NOCOPY VARCHAR2,
X_Msg_Count OUT NOCOPY NUMBER,
X_Msg_Data OUT NOCOPY VARCHAR2,
P_REPAIR_STATUS_Rec IN REPAIR_STATUS_REC_TYPE,
P_STATUS_UPD_CONTROL_REC IN STATUS_UPD_CONTROL_REC_TYPE,
X_OBJECT_VERSION_NUMBER OUT NOCOPY NUMBER) IS
l_api_name CONSTANT VARCHAR2(30) := 'Update_Ro_Status';
l_api_version_number CONSTANT NUMBER := 1.0;
     l_msg_data varchar2(2000);
     l_msg_index_out NUMBER;
BEGIN
-- Standard Start of API savepoint
SAVEPOINT UPDATE_RO_STATUS_PUB;
-- Initialize message list if p_init_msg_list is set to TRUE.
IF FND_API.to_Boolean(p_init_msg_list)
THEN
FND_MSG_PUB.initialize;
END IF;
-- Initialize API return status to success
x_return_status := FND_API.G_RET_STS_SUCCESS;
-- API body
CSD_REPAIRS_PVT.UPDATE_RO_STATUS(P_Api_Version => p_api_version,
P_Commit => p_commit,
P_Init_Msg_List => p_init_msg_list,
P_Validation_Level => FND_API.G_VALID_LEVEL_FULL,
X_Return_Status => x_return_status,
X_Msg_Count => x_msg_count,
X_Msg_Data => x_msg_data,
P_REPAIR_STATUS_REC => p_repair_status_rec,
P_STATUS_CONTROL_REC => p_status_upd_control_rec,
X_OBJECT_VERSION_NUMBER => x_object_Version_number);
-- Check return status from the above procedure call
IF not (x_return_status = FND_API.G_RET_STS_SUCCESS)
then
ROLLBACK TO UPDATE_RO_STATUS_PUB;
return;
END IF;
-- End of API body.
-- Standard check for p_commit
IF FND_API.to_Boolean(p_commit)
THEN
COMMIT WORK;
END IF;
-- Standard call to get message count and if count is 1, get message info.
FND_MSG_PUB.Count_And_Get(p_count => x_msg_count,
p_data => x_msg_data);
     if(x_msg_count > 1) then
          FOR l_index IN 1 .. x_msg_count
          LOOP
          fnd_msg_pub.get (p_msg_index => l_index,
                    p_encoded => fnd_api.g_false,
                    p_data => l_msg_data,
                    p_msg_index_out => l_msg_index_out
          x_msg_data := x_msg_data ||'['||l_msg_data||']';
          END LOOP;
     end if;
EXCEPTION
WHEN Fnd_Api.G_EXC_ERROR THEN
x_return_status := Fnd_Api.G_RET_STS_ERROR;
ROLLBACK TO UPDATE_RO_STATUS_PUB;
Fnd_Msg_Pub.Count_And_Get(p_count => x_msg_count,
p_data => x_msg_data);
IF (Fnd_Log.level_error >= Fnd_Log.g_current_runtime_level)
THEN
Fnd_Log.STRING(Fnd_Log.level_error,
'csd.plsql.CSD_REPAIRS_PUB.Update_ro_status',
'EXC_ERROR[' || x_msg_data || ']');
END IF;
     if(x_msg_count > 1) then
          FOR l_index IN 1 .. x_msg_count
          LOOP
          fnd_msg_pub.get (p_msg_index => l_index,
                    p_encoded => fnd_api.g_false,
                    p_data => l_msg_data,
                    p_msg_index_out => l_msg_index_out
          x_msg_data := x_msg_data ||'['||l_msg_data||']';
          END LOOP;
     end if;
WHEN Fnd_Api.G_EXC_UNEXPECTED_ERROR THEN
x_return_status := Fnd_Api.G_RET_STS_UNEXP_ERROR;
ROLLBACK TO UPDATE_RO_STATUS_PUB;
Fnd_Msg_Pub.Count_And_Get(p_count => x_msg_count,
p_data => x_msg_data);
IF (Fnd_Log.level_exception >= Fnd_Log.g_current_runtime_level)
THEN
Fnd_Log.STRING(Fnd_Log.level_exception,
'csd.plsql.CSD_REPAIRS_PUB.Update_ro_status',
'EXC_UNEXP_ERROR[' || x_msg_data || ']');
END IF;
     if(x_msg_count > 1) then
          FOR l_index IN 1 .. x_msg_count
          LOOP
          fnd_msg_pub.get (p_msg_index => l_index,
                    p_encoded => fnd_api.g_false,
                    p_data => l_msg_data,
                    p_msg_index_out => l_msg_index_out
          x_msg_data := x_msg_data ||'['||l_msg_data||']';
          END LOOP;
     end if;
WHEN OTHERS THEN
x_return_status := Fnd_Api.G_RET_STS_UNEXP_ERROR;
Rollback TO UPDATE_RO_STATUS_PUB;
IF Fnd_Msg_Pub.Check_Msg_Level(Fnd_Msg_Pub.G_MSG_LVL_UNEXP_ERROR)
THEN
Fnd_Msg_Pub.Add_Exc_Msg(G_PKG_NAME, l_api_name);
END IF;
Fnd_Msg_Pub.Count_And_Get(p_count => x_msg_count,
p_data => x_msg_data);
IF (Fnd_Log.level_exception >= Fnd_Log.g_current_runtime_level)
THEN
Fnd_Log.STRING(Fnd_Log.level_exception,
'csd.plsql.CSD_REPAIRS_PUB.Update_ro_status',
'SQL MEssage[' || SQLERRM || ']');
END IF;
     if(x_msg_count > 1) then
          FOR l_index IN 1 .. x_msg_count
          LOOP
          fnd_msg_pub.get (p_msg_index => l_index,
                    p_encoded => fnd_api.g_false,
                    p_data => l_msg_data,
                    p_msg_index_out => l_msg_index_out
          x_msg_data := x_msg_data ||'['||l_msg_data||']';
          END LOOP;
     end if;
End Update_ro_status;
-- R12 Development End
End CSD_REPAIRS_PUB;
Plzz checkout help me out

Programmatically adding/deleting users to/from portal groups

I am using the following PDK api, to delete an user from a portal group (otp_sales).
I get the following error which doestn make sense. I tested the following api from a
script shown below. In my application, this gets called from a trigger, and fails
because it sees a ROLLBACK getting used in the API.
<<<<<<<<<<<<< delete_from_group.sql >>>>>>>>>>>>>>>>>>>>>>
DECLARE
BEGIN
moc.wwsec_api.delete_user_from_list (p_group_id
=>MOC.wwsec_API.GROUP_ID('OTP_SALES')
,p_member_person_id =>73);
END;
<<<<<<<<<<<<<<<<<<<<<<<<<<>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
SQL> @delete_from_group.sql
Input truncated to 1 characters
DECLARE
ERROR at line 1:
ORA-01086: savepoint 'DELETEUSERFROMLIST_SAVEPOINT' never established
ORA-06512: at "MOC.WWSEC_API", line 2467
ORA-06510: PL/SQL: unhandled user-defined exception
ORA-06512: at "MOC.WWCTX_SSO", line 849
ORA-06510: PL/SQL: unhandled user-defined exception
ORA-06512: at "MOC.WWCTX_SSO", line 669
ORA-06502: PL/SQL: numeric or value error
ORA-06512: at line 3
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Thanks
regards
-Ananth

We had the same problem and it turned out that deleting a portal user(delete_portal_user), removing a portal user from a list (delete_user_from_list) or updating a portal user, the "savepoint xxxx never established message" came up when there was no context set. If the procedure is called from within a portal page (or as user portal30) ,and the context is set and it works. The solution is to check to see if the context was set, and then set it if not.
if not portal30.wwctx_api_private.is_context_set then
portal30.wwctx_api_private.set_context(p_user_name => 'portal30');
end if;
Hope this helps
Tania

ORA-01086: savepoint 'DBLINKTEST' never established

Similar Messages

Maybe you are looking for