1-Signon password failure limit
2-Signon Password Length
3-Signon Password No Reuse
4-Signon Password Hard to Guess
For the first one it means how many time can I try to access the system using wrong password. It is recommended to change this value to 3. The default value is null.
The second one to allow minimum password length. The default value is 5, it is recommended to make it 6 or 7.
The 3rd profile is for not allowing using same password again for specified number of days.
The default value for 4th profile option is No. Following are the password rules if the value is set to Yes
1) The password contains at least one letter and at least one number.
2) The password does not contain the username.
3) The password does not contain consecutively repeating characters.
Reference: Metalink Note 362663.1
A company has a code(Package, Procedure, Function etc) with all the proprietary information and logic in it. If this information is leaked out in the market then the competitors can take advantage of it and this can affect the business. One of the way to deal with this is to hide the code from others.
This can be achieved using oracle’s WRAP utility. The advantage of WRAP utility is that this converts the source code into some language that is not understood but the code can still be compiled like any other source code.
Using Wrap is very simple. In the bin directory of Oracle Home, the wrap utility is installed. The file name could be WRAP.exe or WRAP80.exe depending on the oracle version installed.
C:orantBIN>wrap.exe iname=[inputfilename] oname=[outputfilename]
C:orantBIN>wrap.exe iname=wrap_test.sql oname=wrap_test.plb
An example of using WRAP
Create a sample procedure wrap_test using following code
CREATE OR REPLACE PROCEDURE wrap_test
dbms_output.put_line(‘Wrap test complete’);
then call the wrap utility using following
wrap.exe iname=wrap_test.sql oname=wrap_test.plb
Content of new file wrap_test.plb
CREATE OR REPLACE PROCEDURE wrap_test wrapped
It is very clear from this that the new code is not readable and so is completely hidden from others.
Drop your procedure(if already created) and recreate using the the new file wrap_test.plb which can be compiled as any other package. Important point here is that the source code will be hidden and cannot be read.
Another important point to remember is that once wrapped, a code cannot be unwrapped.
- R12 – How to Delete Oracle AR TransactionsMarch 22, 2019 - 8:37 pm
- How to Define Custom Key Flexfield (KFF) in R12January 19, 2018 - 5:43 pm
- AutoLock Box Concepts In R12November 10, 2017 - 8:30 am
- R12 – java.sql.SQLException: Invalid column type in OAFSeptember 15, 2017 - 9:39 am
- How to Find Duplicate Row in OAF Page?April 26, 2017 - 5:17 pm