Using the BEE_DATA credentials gives us access to all the data email migration products do not take.
Recently though we had someone who inherited their Beehive installation and did not have their BEE_DATA password.
Yuck! Normally we do not like to advise things like just changing the password on a running system, since you have no idea what else it affects. As Buckaroo Banzai advised: "No, no, no, don't tug on that. You never know what it might be attached to."
This script will create a user called “sumatraTestBeeData” with all the privileges we need.
--------------------------------------------------------------------------------------------------------------------------
--Using SQL*Plus,
connect sys as sysdba/PASSWORD;
select tablespace_name, status, contents from user_tablespaces where tablespace_name like 'bee_%';
drop user sumatraTestBeeData;
--create user command:
CREATE USER sumatraTestBeeData IDENTIFIED BY PASSWORD DEFAULT TABLESPACE BEE_DATA TEMPORARY TABLESPACE temp QUOTA UNLIMITED ON users QUOTA UNLIMITED ON BEE_DATA;
grant sysdba to sumatraTestBeeData;
grant create session to sumatraTestBeeData;
grant ALL privilege to sumatraTestBeeData;
Grant UNLIMITED TABLESPACE to sumatraTestBeeData;
--sumatraTestBeeData needs access to these three tablespaces:
--BEE_DATA, BEE_LOBS, BEE_INDEX
alter user sumatraTestBeeData quota UNLIMITED on BEE_DATA;
alter user sumatraTestBeeData quota UNLIMITED on BEE_LOBS;
alter user sumatraTestBeeData quota UNLIMITED on BEE_INDEX;
--------------------------------------------------------------------------------------------------------------------------
Then use these Beehive credentials in bCalReader:
No comments:
Post a Comment