Introduction to Worked in functions in plsql

Worked in Functions PL/SQL gives numerous ground-breaking capacities to assist you with controlling information. You can utilize them anyplace articulations of a similar kind are permitted. Besides, you can settle them. The inherent capacities fall into the accompanying classes: blunder detailing capacities, number capacities, character capacities, change capacities, information capacities, incidental capacities You can utilize all the implicit capacities in SQL explanations with the exception of the mistake announcing capacities SQLCODE and SQLERRM. Moreover, you can utilize every one of the capacities in procedural explanations with the exception of the various capacity DECODE. Most capacities are equivalent to those examined in the SQL Reference area aside from the ones that are talked about beneath. Two capacities, SQLCODE and SQLERRM, give you data about PL/SQL execution blunders. (SQLCODE) work SQLCODE return NUMBER Returns the number related with the most as of late raised exemption. This capacity is important just in an exemption handler. Outside a handler, SQLCODE consistently returns zero. For inner exemptions, SQLCODE restores the quantity of the related ORACLE blunder. The NUMBER that SQLCODE returns is negative except if the ORACLE mistake is "no information found", in which case SQLCODE returns +100. For client characterized special cases, SQLCODE returns +1 except if you utilized the pragma EXCEPTION_INIT to connect the exemption with an ORACLE mistake number, in which case SQLCODE restores that blunder number. sql online training (SQLERRM) work SQLERRM [(error_number NUMBER)] return CHAR Returns the mistake message related to the present estimation of SQLCODE. SQLERRM is important just in an exemption handler. Outside a handler, SQLERRM with no contention consistently restores the message ''ORA-0000: normal, effective finish.'' For inner exemptions, SQLERRM restores the message related to the ORACLE blunder that happened. The message starts with the ORACLE mistake code. For client characterized exemptions, SQLERRM restores the message ''User-Defined Exception'' except if you utilized the pragma EXCEPTION_INIT to connect the special case with an ORACLE blunder number, in which case SQLERRM restores the comparing mistake message. You can pass the contention error_number to SQLERRM, in which case SQLERRM restores the message related to error_number. The accompanying various capacities might be useful to you in PL/SQL codingrn(UID) work UID return NUMBER Returns the extraordinary recognizable proof number appointed to the present ORACLE client. UID takes no contentions. (USER) work USER return VARCHAR2 Returns the username of the present ORACLE client. The client takes no contentions. (USERENV) work USERENV (str VARCHAR2) return VARCHAR2 Returns data about the present session. You can utilize the data to compose an application review trail table or to decide the language and character set are in use.\\ The string str can have any of the accompanying qualities: 'ENTRYID' restores an evaluating section identifier 'LANGUAGE' restores the language, region, and database character set being used 'sessionid' restores the examining session identifier 'TERMINAL' restores the working framework identifier for the session terminal You can't indicate the 'ENTRY' or 'session' alternative in SQL explanations that entrance a remote database.you can learn more on pl sql throguh pl SQL training