Please enable JavaScript to view this site.

Estate Forums

Navigation: Invantive Estate > Installatie Server > Omgeving Dupliceren

Duplicate Environment using an Export Schema

To duplicate an environment using a schema export makes it possible to change the names of the schemas involved.

Perform the following steps to copy an environment, for example, by copying production back to test:

Create a configuration file.

Create the users and tablespaces with bubs_create.bat.

Install the database of Invantive Estate till the instantiate objects if the target environment is used for the first time.

Export the data to a file with the statements:

 

set NLS_LANG=AMERICAN_AMERICA.AL32UTF8

exp userid=pbubs/pbubs@orcl buffer=1000000 file=pbubs.dmp grants=no log=pbubs_exp.log consistent=yes

 

In the first ten lines of the log file check that there has been no conversion of characters between character sets.

Stop Microsoft IIS and Apache Tomcat for the target environment.

Clear the target environment: delete all old tables, sequences, views, functions, procedures, triggers and packages.

Upload the file in the new environment based upon an export made by the owner of the application:

 

set NLS_LANG=AMERICAN_AMERICA.AL32UTF8

imp userid=tbubs/tbubs@orcl buffer=1000000 file=pbubs.dmp log=imp_bubs.log full=y ignore=y

 

Check that all objects are valid and check that the counts concerning numbers of objects between the environments are correct, for instance with the following query:

 

select owner

,      count(*)

,      object_type

,      status

from   dba_objects

where  owner like '%BUBS'

group

by     owner

,      object_type

,      status

/

 

Copy the rights by executing the following script as being the Invantive Estate application owner (in this example pbubs). Do replace OLD and NEW by the right schema names:

 

set pages 0

set feedback off

set lines 500

set trimspool on

spool grt.sql

select replace

      ( replace

        ( 'grant '

          || privilege

          || ' on '

          || table_name

          || ' to '

          || grantee

          || ';'

        , 'OUD'

        , 'NIEUW'

        )

      , 'OUDITGEN'

      , 'NIEUWITGEN'

      )

      txt

from   user_tab_privs

where  1=1

and    grantee <> 'OUD'

/

spool off

exit

 

Then, log on as the new Invantive Estate application owner NEW under Oracle SQL*Plus and execute the script:

 

connect NIEUW@orcldb01

@grt

 

Add the needed synonyms under Oracle SQL*Plus:

 

connect NIEUW_tomcat@DATABASEID

begin

 <BUBS OWNER>.bubs_maintain_my_synonyms('<BUBS OWNER>');

end;

 

Finally, copy the software from the Tomcat webapps tree to the target server:

 

cd /opt/tomcat/webapps

mv bubstarget /tmp/bubstarget

cp -pr bubssource bubstarget

 

Do not forget to enter the correct passwords into site.properties and to adjust the URL's. See Site.properties.

Restart Invantive Estate:

 

/etc/init.d/bubs3 restart

 

Open the application as user ‘system’.

Change in settings the description of the environment.

Adapt the profile options.

Change in the screen financial Administrations, the administration from where data is uploaded.

If necessary, change the passwords of all users with an SQL update:

 

connect NIEUW_tomcat@DATABASEID

 

begin

 bubs_session.set_session_info(null, null, 'system', null, null, null, null);

end;

/

 

update bubs_gebruikers_v

set    gbr_wachtwoord='test'

where  gbr_wachtwoord is not null

/

commit

/

 

Delete all documents from the document folder of the target environment.

Copy the documents in the document folder of the source environment to the target environment.

Link the documents to the new directory:

 

update bubs_documenten_v

set    dct_bestandsinhoud=bfilename('<NIEUW_DCT>', bubs_get_bfile_filename(dct_bestandsinhoud))

where  bubs_get_bfile_directory(dct_bestandsinhoud) <> '<NIEUW>_DCT'

and    dct_bestand_url is null

/

commit

/

 

Update the license as user ‘system’.

X

Important Safety and Usage Information

Intended Use and Limitations: This software, developed by Invantive, is designed to support a variety of business and information technology data processing functions, such as accounting, financial reporting an sales reporting. It is important to note that this software is not designed, tested, or approved for use in environments where malfunction or failure could lead to life-threatening situations or severe physical or environmental damage. This includes, but is not limited to:

  • Nuclear facilities: The software should not be used for operations or functions related to the control, maintenance, or operation of nuclear facilities.
  • Defense and Military Applications: This software is not suitable for use in defense-related applications, including but not limited to weaponry control, military strategy planning, or any other aspects of national defense.
  • Aviation: The software is not intended for use in the operation, navigation, or communication systems of any aircraft or air traffic control environments.
  • Healthcare and Medicine Production: This software should not be utilized for medical device operation, patient data analysis for critical health decisions, pharmaceutical production, or medical research where its failure or malfunction could impact patient health.
  • Chemical and Hazardous Material Handling: This software is not intended for the management, control, or operational aspects of chemical plants or hazardous material handling facilities. Any malfunction in software used in these settings could result in dangerous chemical spills, explosions, or environmental disasters.
  • Transportation and Traffic Control Systems: The software should not be used for the control, operation, or management of transportation systems, including railway signal controls, subway systems, or traffic light management. Malfunctions in such critical systems could lead to severe accidents and endanger public safety.
  • Energy Grid and Utility Control Systems: This software is not designed for the control or operation of energy grid systems, including electrical substations, renewable energy control systems, or water utility control systems. The failure of software in these areas could lead to significant power outages, water supply disruptions, or other public utility failures, potentially endangering communities and causing extensive damage.
  • Other High-Risk Environments: Any other critical infrastructure and environments where a failure of the software could result in significant harm to individuals or the environment.

User Responsibility: Users must ensure that they understand the intended use of the software and refrain from deploying it in any setting that falls outside of its designed purpose. It is the responsibility of the user to assess the suitability of the software for their intended application, especially in any scenarios that might pose a risk to life, health, or the environment.

Disclaimer of Liability: Invantive disclaims any responsibility for damage, injury, or legal consequences resulting from the use or misuse of this software in prohibited or unintended applications.

  
Disclaimer