Even if the password_verify_function limit of a profile is changed in Oracle databases, it does not change as requested and changes to “FROM ROOT”. The reason for this problem is that the FLAGS value in the “profname$” data dictionary is 1 for that profile. When this value is updated to 0, the profile limit can be changed without any problems.<\/p>\n
When you want to change the profile limit as follows, the value appears as FROM ROOT.<\/p>\n
SQL> alter profile users limit password_verify_function custom_verify_function;<\/pre>\nWhen the relevant profile limit is checked, it will appear as FROM ROOT.<\/p>\n
SQL> select * from dba_profiles where resource_name='PASSWORD_VERIFY_FUNCTION';\n\nPROFILE RESOURCE_NAME RESOURCE LIMIT COM \n-------- ------------------------- -------------- ---------------- ---- \nDEFAULT PASSWORD_VERIFY_FUNCTION PASSWORD NULL NO \nUSERS PASSWORD_VERIFY_FUNCTION PASSWORD FROM ROOT YES<\/pre>\nWhen we check the flags value of the related profile, it is seen that it is 1.<\/p>\n
select * from profname$; \n\nPROFILE# NAME FLAGS \n---------- ------------------------- ---------- \n0 DEFAULT 0 \n1 USERS 1<\/pre>\nIf the flags of the profile are updated as follows, the problem will be resolved.<\/p>\n
SQL> update profname$ set flags=0; \nSQL> commit;<\/pre>\nWe need to see it updated when we check again.<\/p>\n
select * from profname$; \n\nPROFILE# NAME FLAGS \n---------- ------------------------ ---------- \n0 DEFAULT 0 \n1 USERS 0<\/pre>\nThen, when we alter the profile again, the limit will change successfully.<\/p>\n
SQL> alter profile users limit password_verify_function custom_verify_function;<\/pre>\nWhen we check the profile, we can see it changed.<\/p>\n
Select * from dba_profiles where resource_name='PASSWORD_VERIFY_FUNCTION';\n\nPROFILE RESOURCE_NAME RESOURCE LIMIT COM \n-------- ------------------------- -------------- ---------------- ---- \nDEFAULT PASSWORD_VERIFY_FUNCTION PASSWORD NULL NO \nUSERS PASSWORD_VERIFY_FUNCTION PASSWORD CUSTOM_VERIFY_FUNCTION YES<\/pre>\n\n<\/div>\n