1 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
2 "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
3 <html xmlns="http://www.w3.org/1999/xhtml" id="sixapart-standard">
5 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
6 <meta name="generator" content="Movable Type 5.2.3" />
8 <link rel="stylesheet" href="http://defaria.com/blogs/Status/styles-site.css" type="text/css" />
9 <link rel="alternate" type="application/atom+xml" title="Atom" href="http://defaria.com/blogs/Status/atom.xml" />
10 <link rel="alternate" type="application/rss+xml" title="RSS 2.0" href="http://defaria.com/blogs/Status/index.xml" />
12 <title>Status for Andrew DeFaria: More fun with SQL ANYWHERE</title>
14 <link rel="start" href="http://defaria.com/blogs/Status/" title="Home" />
15 <link rel="prev" href="http://defaria.com/blogs/Status/archives/000539.html" title="Build bugs, Test suite still not runing nightly" />
16 <link rel="next" href="http://defaria.com/blogs/Status/archives/000541.html" title="Production User Database Migrated" />
22 <script type="text/javascript" src="http://defaria.com/blogs/Status/mt-site.js"></script>
24 <body class="layout-one-column" onload="individualArchivesOnLoad(commenter_name)">
26 <div id="container-inner" class="pkg">
29 <div id="banner-inner" class="pkg">
30 <h1 id="banner-header"><a href="http://defaria.com/blogs/Status/" accesskey="1">Status for Andrew DeFaria</a></h1>
31 <h2 id="banner-description">Searchable status reports and work log</h2>
36 <div id="pagebody-inner" class="pkg">
38 <div id="alpha-inner" class="pkg">
40 <p class="content-nav">
41 <a href="http://defaria.com/blogs/Status/archives/000539.html">« Build bugs, Test suite still not runing nightly</a> |
42 <a href="http://defaria.com/blogs/Status/">Main</a>
43 | <a href="http://defaria.com/blogs/Status/archives/000541.html">Production User Database Migrated »</a>
47 <div class="entry" id="entry-540">
48 <h3 class="entry-header">More fun with SQL ANYWHERE</h3>
49 <div class="entry-content">
50 <div class="entry-body">
51 <h3>Attempting to transfer databases using MS Access</h3>
53 <p>OK, trying this methodology:</p>
56 <li>Used installutil copyschemarepo command to copy schema.db ->
58 <li>Moved schema.mdb to new server</li>
59 <li>Used installutil copyuserdb command to copy salira_test.db ->
61 <li>Moved test.db to new server</li>
62 <li>Tried several times to use installutil command to copy
63 salira_bugs.db (the production database) -> bugs2.db. System aborted
64 several times. Not sure if this is due to bad disk blocks or not. This
65 is a major problem as this is the data we care about.</li>
68 <p>Back on the new server:</p>
71 <li>If I do Connection: New and point to the schema.mdb file it wants
72 to overwrite it! Instead I did File: Import Profile of a profile of the
73 old databases. Of course these say SQL_ANYWHERE. I change this to
74 MS_ACCESS and point to the schema.mdb file and this seems to work.</li>
75 <li>Attempt to do Schema Repository: Move. In doing so I set the
76 Physical Database Name by browsing to the folder via the ellipsis
77 button. This leaves me with D:\Clearquest\schema.db. Clicking on Finish
79 <blockquote>The filename you have specified is not a Share. If
80 other users will need access to this database, you should browse
81 through "Network Neighborhood" to place is in a share. Continue with
84 I select No because I do want other users to be able to access this
85 database. Next I change the D:\Clearquest\salira.db ->
86 \\sons-sc-cc\Clearquest\schema.db and click Finish. At this point I get
87 a error dialog stating that it was "Unable to connect to the database
88 server". After much scratching of the head I realize that I should use
89 D:\Clearquest\schema.db, ignore the warning, then go back in and set
90 the Physical Database Name to \\sons-sc-cc\Clearquest\schema.db.<br>
92 Oh, a side issue: After failing using a Physical Database Name of
93 \\sons-sc-cc\Clearquest\schema.db the Rational Clearquest Maintenance
94 Tool still creates a schema.db file. If you go Back and correct the
95 Physical Database Name to a local path and click Finish you'll get a
96 database I/O error. Turns out you have to remove this schema.db file
97 first. These two (what else could I call them but) BUGS caused me to
98 lose many hours of sleep.<br>
100 Managed to move the schema.mdb -> schema.db.</li>
101 <li>Switching to the Clearquest Designer now to Database: Update User
102 Database Properties. As I only have the test.mdb file to convert I
103 change the user database properties for the test database.</li>
104 <li>Now I select Database: Move User Database to move the test user
105 database to SQL_ANYWHERE</li>
108 <p>At this point I'd like to run Clearquest Designer and do Test Work so I
109 can at at least verify that I can access the converted to SQL_ANYWHERE
110 test.db. Unfortunately there is a checked out version of the schema in
111 the schema database that I copied over and I'm not the owner of that
112 checked out schema. And I can't login as that user.</p>
114 <p>By chance I tried Schema Repository: Upgrade: Selected connection in
115 the Clearquest Maintenance Tool and in stepping through those dialog
116 boxes it say "The schema repository that you want to upgrade has
117 checked-out schemas. If you continue the upgrade process, the checked
118 out schema versions cannot be upgraded and will be deleted from the
119 system". I continue onward and manage to "upgrade" the schema and test
120 database. I proceed into Clearquest Designer and manage to Test Work
121 and viola! I got it up. I am nothing if not tenacious!</p>
123 <p><b>Total Time:</b> 2 hours</p>
125 <div id="more" class="entry-more">
129 <p class="entry-footer">
130 <span class="post-footers">Posted by on April 12, 2006 10:50 PM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000540.html">Permalink</a>