Upgrading Beehive 1.3.1 to 1.4.1 – not just yet.
OK. Oracle Homes backed up, check. Database backed up, check. Beehive1.4.1 software downloaded and extracted, check.
I’m in a bit of a dilemma though… Do I upgrade my 1.3.1 to 1.4.1, or just do a fresh install of 1.4.1? In my Post install config, you’ll notice I’m not quite up to configuring and testing Mail. So is doing an upgrade really worth seeing with my measly 2 users. I suppose theoretically it shouldn’t matter if I’ve got 2 or 20,000 users, or any data stored for these users. I mean, obviously the timing may differ (I assume), but I doubt you the reader would be wondering how long it takes me to do an upgrade, (that’s why you have test systems – do it yourself). So, 1.4.1 install would be cleaner.
Before we get to that, I kind of need to warn you about something, I’ve only just found it, and therefore haven’t found the solution yet.
I can’t log in as beeadmin….
I know I know, it’s just a small issue. I didn’t notice the other day after finishing the LDAP sync (as I was just excited to get it working). I hadn’t had a chance until now to look at the environment to get ready for the Beehive 1.4.1 upgrade. (Those long time readers know I’m an Oracle Consultant, so I only get to play with Beehive after hours.)
I tried logging in as beeadmin. It didn’t work, I thought I’d had the wrong password, (being a Consultant, you have to remember dozens of passwords). So went to change the password. Which then meant spending the next 1/2 hour figuring out if I had the right syntax. Every time I ran
[orabee@radium ~]$ beectl modify_user –user loginid=beeadmin –login_password
I got:
[orabee@radium ~]$ beectl command failed. See the log file for more details.
Profile doesnot have attribute mapping
Looking at the log I don’t see much at all… Even when I fire it up with –log_level FINER I couldn’t see anything pinpointing the error, so I’m assuming there’s something wrong with my map between LDAP and UDS.
Maybe that’s why I can’t log in as beeadmin…Back I go.
[orabee@radium ~]$ beectl modify_property –component _AuthenticationService –name AuthStoreType –value db
[orabee@radium ~]$ beectl activate_configuration ; beectl modify_local_configuration_files
Tried logging in again as beeadmin, which… of course, works with the password I thought it was. Hmmm.
OK, so where does that leave me. My beeadmin password was correct after all, and if I tie in OID again, it’s not going to let me log back in because of this attribute mapping issue.
Time to pull apart and rebuild my map. I’ll let you know how I go.
If you have any suggestions, let me know.
Tags: Attribute, Beehive, Check Database, Check Software, Dilemma, Dozens, Environment, Long Time, Mail, Map, Oracle, ORACLE BLOGS, Oracle Consultant, Passwords, Radium, Software Downloaded, Sync, Syntax, Test Systems, Time Readers