-
What are the prerequisites of dbMaestro TeamWork Server?
- Windows operating system (32 and 64 bits):
- Windows 2003 service pack 2 and later
- Windows 2008 R2
- .Net Framework 3.5 SP1 [download]
- Oracle Data Access Provider (ODAC)
- Oracle 10g ODAC version 10.2.0.2.21 (or later) 32 bits [download]
- Oracle 11g ODAC 32 bits [download]
- Access to TeamWork server using TCP port 8010 and 8012
- Access to the Oracle database that will serve as the TeamWork repository
- Access to the managed Oracle databases
- Open firewall ports 8010 and 8012 for incoming TCP connections
- Hardware (Minimum requirements):
- Disk – 5GB (30GB if Oracle repository is on the same server)
- RAM – 2GB (4GB if Oracle repository is on the same server)
- CPU – 2CPU (4CPU if Oracle repository is on the same server)
-
What are the prerequisites of dbMaestro TeamWork Client for Oracle?
- Windows operating system (32 and 64 bits):
- Windows XP
- Windows 2003 service pack 2 and later
- Windows 7
- Windows 2008 R2
- .Net Framework 3.5 SP1 [download]
- Oracle Data Access Provider (ODAC)
- Oracle 10g ODAC version 10.2.0.2.21 (or later) 32 bits [download]
- Oracle 11g ODAC 32 bits [download]
- Access to the Oracle database that will serve as the TeamWork repository
- Access to the managed Oracle databases
- Hardware (Minimum requirements):
- Disk – 5GB
- RAM – 2GB
- CPU – 1CPU
-
What are the requirements for dbMaestro TeamWork Repository?
- Oracle Database 10g release 2 (standard or enterprise edition)
- Oracle Database 11g (standard or enterprise edition)
- Oracle Client installed
- It is recommended that the repository is at the same Oracle version or later than any of the managed Oracle databases
- Hardware (Minimum requirements):
- Disk – 30GB
- RAM – 4GB
- CPU – 4CPU
-
Which Oracle versions does dbMaestro TeamWork for Oracle support?
dbMaestro TeamWork for Oracle supports Oracle database 11g and Oracle 10g release 2 and above
-
How do I enter a new License?
For a permanent license you need to obtain a license from dbMaestro ltd. Or you can extend your temp license using our
websiteIn order to obtain a permanent license, you need to:
- Open the Management Studio. Select the Update License option in the Help menu
- Send to your sales representative the file \TeamWorkOracleClient\License\dbMaestro_installation_id.lic
- Once you get the permanent license file from dbMaestro, you should open the Management Studio. Select the Update License option in the Help menu (the screen below will open) and click on the Load Activation Key File and then click on the Activate dbMaestro button
-
How do I review the license details?
Open the Studio Management. Select the License Details option in the Help menu
-
Which ports does dbMaestro TeamWork for Oracle use? Can I change them?
dbMaestro TeamWork for Oracle uses ports 8001 – 8012 (except for ports 8007, 8009) for communication between the client and server. Changing the ports is not recommended. In case the ports must be changed, contact your regional support representative for instructions
-
Where can I find the server installation log files?
The installation log files are created in TeamWork installation directory. The following describes what can be found in each file:
- \Server_Setup.Log – has the flow of the server installation
- \DB_Setup.Log – has the flow of the repository installation
- \DBLog\dbMaestroTeamWorkManageDB*.log –logs of creating the database objects in TWManageDB schema in the TeamWork repository
- \DBLog\ManageDB-ReCompile.log – recompile log of invalid objects in TWManageDB schema in the TeamWork repository
- \DBLog\ dbMaestroTeamWorkVersion*.log –logs of creating the database objects in TWVersionDB schema in the TeamWork repository
- \DBLog\VersionDB-ReCompile.log – recompile log of invalid objects in TWManageDB schema in the TeamWork repository
- \DBLog\TestConnection.log – Verify that a connection to the repository was established successfully
-
Where can I find the log files of the client installation?
The installation log files are created in TeamWork installation directory. The following describes what can be found in each file:
- \Client_Setup.Log – has the flow of the client installation
- \DB_Setup.Log – has the flow of the repository version confirmation
-
Does TeamWork™ change or add objects to my schemas?
No. TeamWork™ creates its own small schema on each managed instance, but it does not add or change anything in the users’ objects.
-
Does TeamWork™ require an agent to be running on my database server?
No. TeamWork™ uses a three-tier architecture where the third tier is the database itself. There is no additional dbMaestro TeamWork™ software running on the database server.
-
Where can I find the log files of dbMaestro TeamWork client?
The log files created in the specific directory in the client installation directories. The following describes what can be found in each log file:
- dbMaestroTWSidebarError.log – log of errors which occurred in the Side Bar
- dbMaestroTWAdminAgentUIError.log – log of errors which occurred in the Admin
- dbMaestroTWDeploymentErrors.log – log of errors which occurred in Deployment Manager
- systemInfo.log – document the configuration of the system
- dbMaestroTWMSAddinError.log– log of errors which occurred in the Add-In
-
One of my objects is locked by another team member, is there a way to release it?
In case the check-out user cannot check-in the object or undo the check-out, a dbMaestro TeamWork administrator can force a check-in or undo the check-out, thereby releasing the object to the other team members. The dbMaestro TeamWork administrator can force undo check-out or check-in in the Management Studio.
-
I removed objects from source control but they still appear in TeamWork, why?
The change history of an object is kept in the repository even if the object has been removed from source control, in case it will later be added again to source control. Objects that were removed from source control will be displayed in the objects' tree (as will objects that were never added to source control). You can use the filter and disable the PreChecked option in order to display in the objects' tree only the objects that are managed. Before disabling the PreChecked option, it is recommend to enable the Automatically Add New Database Object to Source Control in Administration Settings menu.
-
Why do dropped objects still appear in TeamWork?
The change history of an object is kept in the TeamWork repository even if it has been dropped in Oracle in case it will later be created again and be added to source control. In this case keeping the history of the object is important to reflect the previous changes made on this object. You can use the filter and disable the Deleted in Check-Out State option in order to hide the dropped objects from the objects' tree.
-
What are the criteria for managing table content?
dbMaestro TeamWork can manage the content of lookup table(s). This requires the table to have a Primary Key or a Unique Index. Managing content is supported for tables that contain only primitive data types.
-
Why don’t my table triggers show up in the TeamWork™ Triggers folder?
Table triggers are managed in conjunction with the tables they belong to. The TeamWork™ Triggers folder will show only schema triggers and database triggers. Table triggers are checked-in and checked–out with their respective tables.
-
How are table indexes managed?
Indexes (like table triggers) are managed (in TeamWork™) in conjunction with their tables. Indexes are also checked-in and checked–out with their respective tables.
-
Does adding a schema to TeamWork™ cause its objects (tables, triggers, functions, etc.) to be locked?
No. When a schema is initially added to TeamWork™, its objects are not locked. Those schema objects can, however, be saved as part of a “Save Schema Version” operation. In order to lock an object into source control, you need to perform an “Add object to Source Control” operation; this operation can be performed on a single selected object or on all the objects in an entire schema.
-
Can I edit an object’s DDL definition in TeamWork™?
No. TeamWork™ is a Database Source Control application where the objects are checked-in and checked-out. After you check-out an object you can edit it with any Database Editing application.
-
Are TeamWork™ locks applied by a particular Database Editor? If one user checks-out a table and edits it using SQL Developer™, will another user (using Toad™, for example), be able to override the change?
No. The TeamWork™ locks are placed at the database (Oracle) level. These locks will be in place regardless of which Database Editor the user chooses to use.
-
Do my schemas need to be under TeamWork™ control in order to use Deployment Manager?
No. Deployment Manager can deploy unmanaged schemas. It can also compare any combination of two managed or unmanaged schemas.
-
Does Deployment Manager actually update the destination schema in a deploy operation?
No. Deployment Manager creates a deployment script which can then be run against the destination schema to implement the deployment changes. This script can be run through SQL*Plus or any other Database Editor.
-
Does TeamWork™ create/change a copy of the object DDL?
No. TeamWork™ applies the locks (and the check-in and check-out operations) directly to the database objects. The edit operation is performed on the actual database object. There is no temporary DDL to complicate the process.
-
What kind of performance overhead does TeamWork™ impose on my day-to-day database operations?
None (unless you enable table data management). The TeamWork™ processes are only activated when a schema change is made. There is no overhead at all for DML (SQL Insert, Update and Delete) operations.
-
Can my users subvert the SCM locking mechanism by editing a database object outside of TeamWork™?
No. TeamWork™ uses standard database mechanisms to implement and enforce object locking. The locking is enforced at the database-level, regardless of which Database Editor is being used.
-
What is Integration Mode?
Integration mode was created to allow running script(s) with no need to check-out the entire schema. After running the script(s) the user does Resume From Integration mode. At this point dbMaestro TeamWork analyzes all the objects in the schema and only the objects that were changed are placed in check-out mode; objects that were not changed return to check-in (as there is no reason to update their history).
Another scenario that uses the Integration Mode is nightly jobs. The jobs drop and create indexes to fix defragmentation and improve performance. Without this mode, the user would have to check-out all the relevant the objects, run the job(s), then check-in everything; if the job(s) end successfully then the history becomes larger and larger with similar records. Using this mode, the history will not fill up with empty actions.
Entering into Integration mode requires that all objects are checked-in. The user that initiated Integration mode can run the script and can alter any object. Other users cannot perform check-outs and need to wait until the initiating user performs the Resume From Integration State operation.
-
What is Suspend Mode?
Suspend mode was created to disable dbMaestro TeamWork temporary and allow anyone to change the schema while the schema is in Suspend Mode. The difference between Suspend mode and Integration mode (see above) is that in Suspend mode all users can alter the schema while in Integration mode only the initiating user can alter the schema.
-
Where can I find the log files of dbMaestro TeamWork server?
The log files created in the specific directory in the client installation directories. The following describes what can be found in each log file:
- dbMaestroTWController.log – log of errors which occurred in the Controller service
- dbMaestroTWRMS.log – log of errors which occurred in the RMS service
- dbMaestroTWSecurity.log – log of errors which occurred in the Security service
- systemInfo.log – document the configuration of the system
-
What functionality does dbMaestro TeamWork server provide?
dbMaestro TeamWork server has several tasks, including:
- Accepting requests from all clients (check-out, check-in)
- Notify all clients of changes in objects' status
- Communicating with the TeamWork repository database
- Retrieving an object’s DDL or data on check-in operation from the managed schema
- Locking the object on check-out operation on the managed schema
- Performing rollback / undo operations on the managed schema
- Finding created and dropped objects and updating the clients
-
What is the RMS Service?
The RMS service is responsible for communications between the clients, the other TeamWork services and the managed databases; for example, retrieving the object DDL, performing rollbacks, locking an object and so on.
-
What is the Controller Service?
The Controller service is responsible for accepting client requests and notifying the clients about changes in the objects' status. For example, a check-out operation is accepted and handled by the controller and, upon completion, all clients are notified immediately about the status change.
-
What is the Security Service?
The Security service is responsible for finding new objects and dropped objects. It then communicates with the other services, for example with the RMS to add the object to source control if needed, and with the Controller service to notify the clients about new objects which will be reflected in the schema tree in all the clients.
Integration with 3rd party SCM products
-
Which 3rd party SCM products does dbMaestro TeamWork integrate with?
dbMaestro TeamWork integrates with Microsoft Team Foundation Server, IBM Clear Quest and IBM Rational Team Concert out of the box. Custom integrations can be produced on demand with other SCM products like Subversion, SVN and others.
-
What can I get from integration with Microsoft Team Foundation Server?
Integration of TeamWork with Microsoft Team Foundation Server will allow you to update the changes TeamWork records in the TFS repository as well as in TeamWork. You can also assign a check-in to a change-set (i.e. a work item in TFS), thus creating a link between business requirements and the actual change. You can also link a saved version in TeamWork to a label in TFS.
-
What can I get from integration with IBM Rational Team Concert?
Integration of TeamWork with IBM RTC will allow you to update the changes TeamWork records in the RTC repository as well as in TeamWork. You can also assign a check-in to a change-set (i.e. a work item in RTC), thus creating a link between business requirements and the actual change. More information is available in our
website.
-
What can I get from integration with IBM Clear Quest?
Integration of TeamWork with IBM Clear Quest will allow you assign a check-in to a change-set (i.e. a work item in Clear Quest), thus creating a link between business requirements and the actual change.
-
When should I use the TeamWork SCM Provider?
In case you don't have a 3rd party tool that you manage with the requirements, you can use the out-of-the-box the TeamWork CMS provider. Using it will allow you to review changes by change-set (which can be translated into business requirements).
-
What is the method of integrating with RTC and CQ?
-
What is the SDK?
The TeamWork SDK is a platform to invoke dbMaestro TeamWork commands using scripts. You can use it in your build automation scripts, in integration with 3rd party tools such as other SCM products, on automatic deployment generators and so on.
-
What can I do with the SDK?
You can perform check-out all objects or specific object, check-in all objects or specific object, Save Version and Deploy.
-
Where can I find examples how to work with the SDK?
There is a Samples directory in the SDK directory. There are code samples for check-out and check-in.
-
The SDK XML file requires the Project-Id, why is it needed?
The project id is required in the SDK XML configuration file in order to verify that the executing account (the one that invoke the SDK) is authorized to perform the require actions in this schema. You can review the project id in the Properties section when the project is in focus.
-
What is the db API?
The dbAPI is an Oracle package within the managed database which you can call from your Oracle jobs or any other program which accesses the managed databases.
-
What can I do with the db API?
dbAPI supports entering into Integration State and Resume from Integration State, entering into Suspend mode and Resume from Suspend mode and check-in all objects.
-
I want to copy the production database into the development, what should I do in TeamWork?
TeamWork identifies the managed Oracle database base on its dbid. By copying the production database to the development database, there will be inconsistency between dbMaestro TeamWork repository and the managed database. In order to solve that, you need to perform the following steps:
Before the Refresh
- Check in all objects on all schemas in the database
- Save the development database id
- Export the dbmaestro_teamwork schema
The Refresh Action
- Copy the production database to the development database
- Change the database id of the new copy:
- shutdown immediate;
- startup nomount;
- nid target=SYS/]PASSWORD]@[SERVICE NAME]
- startup
- Import the dbmaestro_teamwork schema saved in step #3
After the Refresh
- Stop dbMaestro TeamWork services
- Execute the following commands in the TeamWork repository, replacing [oldb_db_id] and [new_db_id] with the old database id and new database id respectively:
begin tran;
update twmanagedb.tblmonitoredserverinstances
set oracledbid = [new_db_id]
where oracledbid = [old_db_ib];
commit;
- Start TeamWork services
- Open Studio Management
- Perform Check-Out (Structure and Content) to all managed objects in all the schemas in the refreshed database
- Perform Check-In (Structure and Content) to all managed objects in all the schemas in the refreshed database
-
I changed the password of the managed schema, how do I change it in dbMaestro TeamWork also?
The dbMaestro TeamWork clients will ask for the password when you reopen the clients. Please contact dbMaestro support team
support@dbmaestro.com in order to change the password of the managed schema in the server.
-
Why is dbMaestro TeamWork™ has an open connection to my managed schema, even if there is no TeamWork clients open?
dbMaestro TeamWork™ server opens a connection to any managed schema in order to discover new or dropped objects. dbMaestro TeamWork™ uses the connection and examine the metadata every 30 seconds by default.
-
How can I disable TeamWork change policy locking in my database in case dbMaestro TeamWork™ is unavailable?
dbMaestro TeamWork comes out-of-the-box with a special application, answering this rare scenario. You can find this Suspension tool on your TeamWork server at:
<INSTALL directory>\suspend\dbMaestroTeamWorkSuspend.exeAfter lunching this application, you should see the following screen.
You need to use the SYS Oracle account. The Hostname, Port and SID or Service Name are for your Oracle managed database.
You should fill the TeamWork repository parameters in the next screen. You should be aware that once you disable dbMaestro TeamWork change policy enforcement in the database, everyone can perform changes to the database objects.
Once TeamWork return to operational, you have to resume it from the manual suspension by running again this utility.