Webcenter collaboration not starting, error in linked db alias

Question

Hi
I installed webcenter collaboration and at the end I run all the scripts in the oracle db, everything was ok without errors or warnings.
When I try to start collaboration i got an error that say that the linked database alias is not correct.
i test [aluischema].ora. [aluischema].dbo.
both the alui and collaboration user can see those tables.
Which value i must put in the Linked Database Alias parameter on the configuration of collaboration component.. it's the only thing that i dont really know.
any idea ?
thanks

Answer 1

Your database alias should be the SID, i.e. whatever the user name is for your plumtree database. However, you may want to ensure you've created the CollabRead role...
Execute the following as a DBA (system user):
create role CollabRead;
grant CollabRead to <collab DB SID>;
Execute the following as your plumtree database SID:
grant select on plumdbuser.ptvgroupmembership to CollabRead;
grant select on plumdbuser.ptcommunities to CollabRead;
grant select on plumdbuser.ptcommsecurity to CollabRead;
grant select on plumdbuser.ptfolders to CollabRead;
grant select on plumdbuser.ptobjectsecurity to CollabRead;
grant select on plumdbuser.ptusers to CollabRead;
grant select on plumdbuser.ptusergroups to CollabRead;
grant select on plumdbuser.ptmycommunities to CollabRead;
grant select on plumdbuser.ptprefs to CollabRead;
grant select on plumdbuser.ptpropertydata to CollabRead;
grant select on plumdbuser.ptmigration to CollabRead;
grant select on plumdbuser.ptserverconfig to CollabRead;
grant select on plumdbuser.ptobjectproperties to CollabRead;
grant select on plumdbuser.ptlocalizations to CollabRead;
grant select on plumdbuser.ptcards to CollabRead;
grant select on plumdbuser.ptusergroups to CollabRead;
grant select on plumdbuser.ptproperties to CollabRead;
grant select on plumdbuser.ptuserinfomap to CollabRead;
grant select on plumdbuser.ptadminfoldersecurity to CollabRead;
grant select on plumdbuser.ptpages to CollabRead;
Maybe you executed the scripts but didn't create the role, or didn't grant it to the right user?