The relevant query is as follows:
SELECT text
FROM dba_errors
WHERE name = ‘<PACKAGE_NAME>’;
Tuesday, 10 May 2016
Subscribe to:
Post Comments (Atom)
Follow us:
Home » APPS QUERIES » Query to Display Package Errors
Hello There,
ReplyDeleteSeems like I won the lottery here….This is a treasure box of blogs and your folks are like leprechauns! Phenomenal read on Query to Display Package Errors
I have DMLStatements which contains some polish characters for POLAND country.
When I am executing that DML through the QL Developer I am able to see my Polish characters.
but when we gave the release through the SQLPLUS those
characters are replacing with
some special characters
like ? (Question Mark)
Data type of the column is : NCLOB
NLS_CHARACTERSET : AL32UTF8
NLS_NCHAR_CHARACTERSET : AL16UTF16
Could you please help to resolve this?
THANK YOU!! This saved my butt today, I’m immensely grateful.
Kind Regards,
Sindu
Szia,
ReplyDeleteGrazie! Grazie! Grazie! Your blog is indeed quite interesting around Query to Display Package Errors! I agree with you on lot of points!
I posted before regarding using oracle UDT stored procedure parameter type to pass a list of records for multiple insert using .net c#.
I had the below example where a class definition is needed at .net side to map to oracle object. Unfortunately, I did not apply this due to the extra mapping code that is needed.
http://appsjack.blogspot.com.eg/2010/09/pass-custom-udt-types-to-oracle-stored.html
My question is: did this change with oracle 12c? Can we now use:
parameter.UdtTypeName = directOracleUDTName; //without the need for .net definition and mapping classes
Once again thanks for your tutorial.
Best Regards,
Radhey