Andreas' Adventures

When I was extracting some information from an OID I found that the LDIF lines contain a line break. Some searches on the Internet delivered a nice solution from Dan Norris: http://www.dannorris.com/2008/09/08/concatenating-lines-in-ldapsearch-results/ Using that the the ldif file was modified and was reusable for my purpose (creating provisioning profiles for DIP).

Lately I've been doing some AD-OID synchronization. Should be not that difficult, but as so often the devil is in the detail. The AD admin created a user that is capable of reading the complete AD - as it is described in the documentation. Then I tried to login. And tried, and tried. Password was reset, different password was used, etc. No luck. I tried a very easy ldapsearch and received the follwoing error: 80090308: LdapErr: DSID-0C09030B, comment: AcceptSecurityContext error, data 531, v893 HEX: 0x531 - not permitted to logon from this workstation DEC: 1329 - ERROR_INVALID_WORKSTATION (Logon failure: user not allowed to log on to this computer.) LDAP[userWorkstations: ] NOTE: Returns only when presented with valid username and password/credential. Aha, that gave me a clue. So the username and password seemed to be correct. Some googeling established the problem. The user was created but the AD admin did not allow the user to login to the machine where the AD was running.

Ok, I promise I will take more time to read things like manuals and other documents when it comes to new features in the database. Take the Flashback Recovery Area (FRA). Oracle does store archive logs in there, which is cool as it speeds up the recovery. The bad thing is that the Oracle Database behaves like a small child. When you do not look it will do strange things. So I was busy setting up the online backup of an infrastructure database. This one is still in 10.1.x while all the others in this environment are on 10.2.x . For the RMAN I have a catalog (also 10.2.x) so I had some problems with the versions as the 10.1.x database refused to get into the 10.2.x RMAN catalog. I thought that I have plenty of space for the archivelogs in the ASM (everything was RAC of course). I turned my attention to some other issues (aka not watching your kid for a moment). Then during an important demo for the client a developer told me that he cannot use the OID. Of course I checked, but the OID wa...

Using a WebCenter Wiki with a 3rd party LDAP is possible but you have to make sure that the following two groups are present and populated in the LDAP: users oc4j-administrators Also the group search definition must be on Nested. The next picture shows the basic values for the 3rd party LDAP: