Best Of
Re: Orch log
Hi,
Please note I have moved your post CNC, DB and Operating System - JDE1 (MOSC) to Integration Technologies - JDE1 (MOSC).
Thank you,
Elena
Re: Orch log
Hi 2011
Are you talking about switching on the AIS Debug Logs? To do this you need to:
- Sign in to JDE Server Manager
- Navigate to the AIS server instance you want to generate the logs on
- In the navigation pane select Logging from the Configuration panel
- In the Log File Configuration screen click on Create New User Specific Log Configuration and you will be prompted for a user name.
- Enter the JDE user ID you want to log and an entry will be added to the User Specific Log File Configuration list. Update the Log Level Threshold as required and click on Apply to start logging.
If you're asking about seeing the SQL that an Orchestration's Data Request generates then I don't think this is recorded in the AIS logs in the same way that the SQL generated in a UBE's jdedebug.log is - I may be wrong, but I haven't come across any when debugging an Orchestration. Having said that we tend to use Database Connectors to retrieve data within Orchestrations as this allows us to use bespoke SQL and build more advanced queries.
Cheers
Jonathan
MasonJo
Re: Orch log
Hello,
Jonathan is right. The queries made through data request are logged by JAS server.
In case you want to see the queries made through database connectors, the developers creating the script in the connector may use orchAttr.writeWarn to log the query which is executed. The data is logged in the e1root log file of AIS server
Thank you!
Best regards,
Cezar
Re: EXPDP Failing
Hello Bruno & Micheal,
Thanks for your feedback. BTW the Oracle im using is 19.30 on RHEL8
I found the solution for this error:
- The main issue was that the Compatibility is set to 11.2 so i have to change this to 12.2…..we did not attempted this as this error we got in Prd and all of the concerned lower env's are still on 11.2. So we have to test in our lower env before we push this change in prod depending on how application behaves after the change
Instead i did below stuff which worked:
login as sysdba
run the below sql:
SQL> SELECT sequence_name,
last_number
FROM dba_sequences
WHERE sequence_owner = 'SYS'
AND sequence_name = 'AQ$_KUPC$DATAPUMP_QUETAB_1_N';
then run the below scripts - or if not then i have recreate the datapump component
as SYS: @$ORACLE_HOME/rdbms/admin/catdph.sql
@$ORACLE_HOME/rdbms/admin/prvtdtde.plb
@$ORACLE_HOME/rdbms/admin/catdpb.sql
@$ORACLE_HOME/rdbms/admin/dbmspump.sql
@$ORACLE_HOME/rdbms/admin/utlrp.sql - When i run the above scripts it resets the sequnce of AQ and that fixed the expdp error.
SQL> SELECT sequence_name,
last_number
FROM dba_sequences
WHERE sequence_owner = 'SYS'
AND sequence_name = 'AQ$_KUPC$DATAPUMP_QUETAB_1_N';====at this stage the ouput is null - Tried a test expdp it worked and when again ran the above query to see the the sequence value resetted.
Thanks
Ilyas
IHK
Re: EXPDP Failing
hey @IHK
qq: did you start the expdp with "sys as sysdba" , this is not recommended see
https://www.oracle.com/a/ocom/docs/oracle-data-pump-best-practices.pdf
possible solution for your issue might be here:
https://mudasirhakakblog.wordpress.com/2025/04/11/ora-39077-unable-to-subscribe-agent-kupca_1_112549778218000-to-queue-kupcc_1_20240604112547_0/
hth,
michael
Re: EXPDP Failing
Hello IHK,
I never faced this, but I would investigate in the alert logfile to see if it contains something. Also may you provide the Oracle version that you use (and the OS)? And maybe the "copy & paste" of the actual session.
You might try to use a parameter file instead of providing arguments on the command line; you might try to export another table…
Does by any chance your expdp is of version < 12.2 but your database 12.2 or higher and using identifiers (like column name) longer than 30 bytes?
Do you have this for any "expdp" session that you attempt? If "it was OK before", have you recently applied some patches, done something special…
Have also a look at specific patches for datapump related to your Oracle version (https://support.oracle.com/support/?kmContentId=2819284)
HTH,
Bruno Vroman.
P.S. and maybe the simplest: stop+start database and retry ;-)
Re: Can we add more segment on the existing Locator Flexfield ?
Yes , optional should be fine. Are you planning to update the values on existing locators ? Please ensure no transactions are performed on the instance until all locator changes are done and the Stock Locator KFF is compiled successfully.
Re: When is Entreprise Manager 24.1 RU8 going to be released
Hi
if you mean redirect that the menu is not shown again in browser, follow procedure mentioned in
OEM 24ai - RU 07 — oracle-mosc
When I review the release dates, I estimate RU08 in April.
Regards,
Martin
Re: Tax Year 2025: “Get Ready Campaign” for Supplier 1099 Year End Preparations!
Farah, Can you confirm the solution will provide the CSV format file? The SSA specs indicate 2 options to file CSV upload and A2A transmission (XML format).
Re: Tax Year 2025: “Get Ready Campaign” for Supplier 1099 Year End Preparations!
I am not sure where to ask this question. Is there an update for the 1099 Leg/Reg change for the new IRIS portal? Will Oracle provide a JDE E1 update for 2026 reporting?
Beginning with the 2026 tax year (filed in 2027), all electronic filings must be submitted through the new Information Returns Intake System (IRIS). There are a few technical requirements, the new portal will no long accept the ASCII flat file format.