My Tech Lab

Some of the most common issues faced while installing AIA Foundation Pack 2.5 on Oracle Application Server 10.1.3.4 1. Configuration Assistance Failed Solution: In case configuration assistance failed to complete, check the install log under AIA_HOME/logs/Install/FP and correct the issues. Then restart the configuration assistance from SOA_HOME/cfgtools/configToolFailedCommands file. It typically looks like E:\\product\10.1.3.1\OracleAS_1\jdk\bin\java.exe -jar E:\product\10.1.3.1\OracleAS_1/Infrastructure/install/lib/AIAUtils.jar -i E:\product\10.1.3.1\OracleAS_1 -nopips 2. Uninstall option is not available with FP2.5 installer Solution: To uninstall FP you need to use OUI under \Disk1\install. Browse through the Oracle Application Server > Application Integration Architecture 2.5.0.0.0.0 3. AIAReadJMSNotificationProcess compilation fails with following message: ORABPEL-01501 undefined part element. In WSDL at "http:// :8888/orabpel/default/AIAErrorTaskAdministrationProcess/AIA...

SQL> connect sys as sysdba Enter password: Connected to an idle instance. SQL> startup ORA-44412: XE edition memory parameter invalid or not specified SQL> startup pfile=C:\oraclexe\app\oracle\product\10.2.0\server\config\scripts\init.ora ORACLE instance started. Total System Global Area 805306368 bytes Fixed Size 1289996 bytes Variable Size 209715444 bytes Database Buffers 591396864 bytes Redo Buffers 2904064 bytes Database mounted. Database opened. SQL> create spfile from pfile='C:\oraclexe\app\oracle\product\10.2.0\server\config\scripts\init.ora'; File created. SQL> shutdown Database closed. Database dismounted. ORACLE instance shut down. SQL> startup ORACLE instance started. Total System Global Area 805306368 bytes Fixed Size 1289996 bytes Variable Size 209715444 bytes Database Buffers 591396864 byt...

bpel_synch Shared via AddThis

Enqueue Message DECLARE enqueue_options DBMS_AQ.enqueue_options_t; message_properties DBMS_AQ.message_properties_t; msg_handle RAW (16); ipmsg ip_message_type; xml_clob CLOB; msg_id NUMBER (10); subscribers DBMS_AQ.aq$_recipient_list_t; BEGIN xml_clob := ''; subscribers (1) := SYS.aq$_agent (' ' , NULL , NULL); message_properties.recipient_list := subscribers; DBMS_AQ.enqueue (queue_name => ' ' , enqueue_options => enqueue_options , message_properties => message_properties , payload => xml_clob , msgid => msg_handle); COMMIT; END; Dequeue Message DECLARE dequeue_options DBMS_AQ.dequeue_options_t; message_properties DBMS_AQ.message_properties_t; message_handle RAW (16); xml_clob CLOB; BEGIN dequeue_options.consumer_name := ' '; dequeue_options.dequeue_mode := DBMS_AQ.remove; -- Only if you want to remove message dequeue_options.navigation := DBMS_AQ.next_message; dequeue_options.WAIT := DBMS_AQ.forever; DBMS_AQ.dequeue (queue_name => ...

It's explained in the Developer Guide. The ERRBUF is the message that you return and RETCODE is the return code. These two parameters are very much required exactly in the fashion. If the RETCODE is 0 stands for Success, 1 for success with warnings and 2 for Errors. For example you have a stored procedure created as below CREATE PROCEDURE TEST_CONC(ERRBUF OUT VARCHAR2,RETCODE OUT VARCHAR2) AS BEGIN --- PROCESSS ERRBUF := 'Successful Operation'; RETCODE := '0'; EXCEPTION --- EXCEPTION HANDLING ERRBUF := 'Found Exception '; RETCODE := '2'; END;

Example: Gregorian Calendar The following examples show a selection of dates and times and the way they might be formatted. These examples assume the use of the Gregorian calendar as the default calendar. Required Output Expression 2002-12-31 format-date($d, "[Y0001]-[M01]-[D01]") 12-31-2002 format-date($d, "[M]-[D]-[Y]") 31-12-2002 format-date($d, "[D]-[M]-[Y]") 31 XII 2002 format-date($d, "[D1] [MI] [Y]") 31st December, 2002 format-date($d, "[D1o] [MNn], [Y]", "en", (), ()) 31 DEC 2002 format-date($d, "[D01] [MN,*-3] [Y0001]", "en", (), ()) December 31, 2002 format-date($d, "[MNn] [D], [Y]", "en", (), ()) 31 Dezember, 2002 format-date($d, "[D] [MNn], [Y]", "de", (), ()) Tisdag 31 December 2002 format-date($d, "[FNn] [D] [MNn] [Y]", "sv...

The cancellation process is related to processing constraint CANCEL for Order Line entity. 1. To disable it: Navigate to Setup>Rules>Security>Processing Constraints. Use Delete Record from Edit menu to disable the following processing constraints Validation Templates: a) Operation > CANCEL; Validation Template>Pick released b) Operation > UPDATE; Attribute>Schedule Ship Date; Validation Template>Pick released c) Operation > UPDATE; Attribute>Schedule Arrival Date; Validation Template>Pick released 2. Create all conditions from above as new when your business requires to put these constraints back. 3. To enable cancellation, remove this constraint not only from CANCEL operation but also UPDATE operation for some attributes like Ordered Quantity, Request Date, etc. Make sure that this constraint is removed from ALL the attributes.