what are version control tools used in oracle apps?



what are version control tools used in oracle apps?..

Answer / mark

Oracle version control and change control?

Oracle Tips by Burleson Consulting

Question: Are there tools for managing a PL/SQL change
control and version control system? I want to track
versions and also track who changed a PL/SQL stored
procedure and when the PL/SQL was changed.

Answer: There are a variety of third-party Oracle change
control and version control tools

*

Open source tools such as SCCS (Source Code Control
System) for Oracle. This is superseded by the Gnu CSSC
version control software.

*

OEM change control pack from Oracle

*

Oracle's SQL Developer also has an interface for
third-party change control and version control.

*

Merant PVCS (Serena) version control for Oracle

*

Mercury ITG ( Formally Kintana) for Oracle revision,
change control and Oracle version control.

Many folks use open-source tools such as the Source Code
Control System (SCCS), which has a check-in, check-out
routine. Oracle's SQL Developer also has an interface for
change control and version control:

"With 1.1, users can now access these files from their
version control systems," Harper said. "They open them up in
SQL Developer, and then they can edit those files and return
them to their version control system."

Oracle also has SCM (Software control Manager) that has
version control for repository objects with check-in, check
out. The version control is enabled within SCM in the
Repository Administration Utility, where you choose "Options
> Enable Version Support".

Also, Kishore Pagadala has published this code snippet for
tracking PL/SQL code changes:

-- Create history table
CREATE TABLE SOURCE_HIST
AS SELECT SYSDATE CHANGE_DATE, USER_SOURCE.*
FROM USER_SOURCE WHERE 1=2;

-- Store code in hist table
CREATE OR REPLACE TRIGGER change_hist
AFTER CREATE ON SCOTT.SCHEMA
-- Change SCOTT to your schema name

DECLARE
BEGIN
IF DICTIONARY_OBJ_TYPE
IN ('PROCEDURE', 'FUNCTION',
'PACKAGE', 'PACKAGE BODY', 'TYPE') THEN

-- Store old code in SOURCE_HIST table
INSERT INTO SOURCE_HIST
SELECT sysdate, user_source.*
FROM USER_SOURCE
WHERE TYPE = DICTIONARY_OBJ_TYPE
AND NAME = DICTIONARY_OBJ_NAME;
END IF;
EXCEPTION
WHEN OTHERS THEN
raise_application_error(-20000, SQLERRM);
END;

Is This Answer Correct ?    5 Yes 0 No

Post New Answer

More Oracle Apps Technical Interview Questions

In interface process we have 1000 records i want to commit every 100 records how? How i can commit every 100 records?

2 Answers  


what are the types of interfacing?

3 Answers   TCS,


in reports token is casesensitive or not?

2 Answers  


What is MO operating units. Why it need to to set this and where .

2 Answers   IBM,


what is the difference between credit memo and debit memo?...

2 Answers   Sony,


When loading data from staging table to interface table , how to reload the invalid record once again ?

6 Answers   Accenture,


how many groups we can create for query?

3 Answers  


pls send me out bound code of supplers,site,bankiformation code pls as soon as

0 Answers  


what is mean by confine mode and flexi mode?

2 Answers  


Can we run a package with out specification?If yes how?

4 Answers  


define steps of assigning items to an organization.

1 Answers   Scan Steel,


How to develop XML report without rdf?

4 Answers   Oracle,


Categories
  • Oracle Apps Technical Interview Questions Oracle Apps Technical (547)
  • Oracle Apps Financial Interview Questions Oracle Apps Financial (793)
  • Oracle Apps Manufacturing Interview Questions Oracle Apps Manufacturing (53)
  • Oracle Apps HRMS Interview Questions Oracle Apps HRMS (169)
  • Oracle Apps CRM Interview Questions Oracle Apps CRM (9)
  • Oracle Apps SCM Interview Questions Oracle Apps SCM (141)
  • Oracle Install Base Interview Questions Oracle Install Base (62)
  • Oracle Service Contracts Interview Questions Oracle Service Contracts (101)
  • Oracle Apps AllOther Interview Questions Oracle Apps AllOther (114)