For the analysis of various problems, the provision of a detailed description and log files is not always sufficient. This is usually the case when corresponding misbehaviors are caused by the modeling or configurations that are not given in our demo data or cannot be recreated. As a consequence, these behaviors cannot be reproduced by us.
In many cases, however, the provision of complete data is not necessary for a reproduction. Often a MDB with the database schema and configuration is sufficient to reproduce the behavior. Many customers have such a MDB (Param MDB, Master MDB) and it is used and maintained according to the recommendations of Professional Service in the context of schema changes and configuration adjustments.
If such a MDB does not exist, it can be created from an enterprise geodatabase as follows.
- Start ArcCatalog
- Create a new Personal-Geodatabase in ArcCatalog
- If not yet activated, then activate the menu bar 'UT Administration' via 'Customize' -> 'Toolbars'
- Execute task "Install" with the 'UT Database Schema Quick Start'
- Source Geodatabase: Enterprise Geodatabase (*.sde) under usage of the UT schema owner (UTARC)
- Target Geodatabase: newly created Personal-Geodatabase
- Start
- Derive feature classes: No
- Selection of FDS: all or at least relevant ones for the support case
- Start
- Execute task "Exchange UT support data" with the 'UT Database Schema Quick Start'
- Source Geodatabase: Enterprise Geodatabase (*.sde) under usage of the UT schema owner (UTARC)
- Target Geodatabase: Personal-Geodatabase used before that task
- Start
- Selection of Support data: all
- Start
Comments
0 comments
Please sign in to leave a comment.