Monday, April 15, 2013
CSVDE install
Note to self: To get CSVDE you need to install 'Active Directory Lightweight Directory Services' ->
ORA-01882 timezone region not found - Can not connect to database in SQL Developer
Got this nice error when I upgrade my Oracle SQL Developer:
Basically you just need to add a time zone to the SQL Developer Config file (/opt/sqldeveloper/sqldeveloper/bin/sqldeveloper.conf) to resolve. I added the following line:
AddVMOption -Duser.timezone=SAST
AddVMOption -Duser.timezone=SAST
Friday, April 12, 2013
AD Change Password on next Logon
So there seem to be a number of posts on how to set this via Novell IDM. All you really need to do is the the pwdLastSet attribute on a user to 0. Then the next time they log in they will need to change their password. We had a challenge where for certain users on creation we did not what their password to be 'expired'. To acheive this you have to set pwdLastSet to -1. I could not find to many posts on this but this one helped ->
"If the previous value of pwdLastSet is 0, assigning the value -1 results in
Active Directory actually making the value equivalent to the current
date/time (as if the user just changed their password). If the previous
value of pwdLastSet is any other value (even if the password is expired),
assigning the value -1 results in no change. If you want the value of
pwdLastSet to be equivalent to the current time, first assign 0, then
assign -1."
"If the previous value of pwdLastSet is 0, assigning the value -1 results in
Active Directory actually making the value equivalent to the current
date/time (as if the user just changed their password). If the previous
value of pwdLastSet is any other value (even if the password is expired),
assigning the value -1 results in no change. If you want the value of
pwdLastSet to be equivalent to the current time, first assign 0, then
assign -1."
JDBC Driver - Table/view 'TABLENAME' is undefined or unsyncable.
So I was pulling my hair out with this error on the Driver.
I started looking through the changes I'd made to the Driver and could not find anything that would cause this issue. I eventually deployed the backup of the Driver and found the issue still persisted.
At least then I realised the issue was not with the Driver. Someone had made a change to the database to allow for the deletion of records during a cleanup process. They forgot to put the foreign key constraint back for the table. We add the foreign key constraint back to the table, restarted the Driver and we where back in business. The JDBC Driver will not sync data to other tables if the foreign key constraint is not setup correctly.
I started looking through the changes I'd made to the Driver and could not find anything that would cause this issue. I eventually deployed the backup of the Driver and found the issue still persisted.
At least then I realised the issue was not with the Driver. Someone had made a change to the database to allow for the deletion of records during a cleanup process. They forgot to put the foreign key constraint back for the table. We add the foreign key constraint back to the table, restarted the Driver and we where back in business. The JDBC Driver will not sync data to other tables if the foreign key constraint is not setup correctly.
Subscribe to:
Posts (Atom)