System and method for verifying paths to a database

• US 7,908,252 B1
• Filed: 03/19/2008
• Issued: 03/15/2011
• Est. Priority Date: 03/19/2008
• Status: Active Grant

• Current Assignee: CF DB EZ LLC (SoftBank Group Corp.)
• Original Assignee: Crossroads Systems (Texas) Incorporated (Crossroads Systems, Inc.)
• Inventors: Landt, Matthew Eugene, Basiago, Jack
• Primary Examiner(s): Trujillo, James
• Assistant Examiner(s): Casanova, Jorge A
• Application Number:
  US12/051,555
• Time in Patent Office: 1,091 Days
• Field of Search: 707/687, 707/796
• US Class Current: 707/687
• CPC Class Codes: G06F 16/24 Querying

Abstract

Embodiments provide systems and methods for verifying paths to databases. A method for identifying paths to a database may comprise opening a database in a set of databases utilizing a known path to the database, creating an object in the database and checking for the object utilizing one or more paths in a set of paths to databases, wherein paths in the set of paths corresponding to a database containing the alias are paths to the database. By repeating the above process for multiple databases, paths to multiple databases may be verified.

Claims

1. A system comprising a memory storing a set of paths and a controller operable to verify paths to a database, verifying paths to the database comprising:

opening a database utilizing a known path corresponding to the database;

creating a database object in the database; and

for each of the paths in the set of paths, verifying the path by attempting to access the database utilizing the path and determining whether the created database object is present in the database accessed utilizing the path, wherein if the created database object is present in the database accessed utilizing the path, the path is verified as a valid path to the database, and wherein if the created database object is not present in the database accessed utilizing the path, the path is determined to be an invalid path.

2. The system of claim 1, wherein the created database object is a temporary database object which is created during the process of verifying paths to the database and removed from the database upon completion of the process of verifying paths to the database.

3. The system of claim 2, further comprising:

closing the database upon completion of the process of verifying paths to the database.

4. The system of claim 1, wherein determining whether the created database object is present in the database accessed utilizing the path comprises querying for the database object utilizing the path.

5. The system of claim 1, wherein the database object is an alias.

6. A method of verifying paths to a database, comprising:

opening a database utilizing a known path corresponding to the database;

creating a database object in the database; and

for each of the paths in the set of paths, verifying the path by attempting to access the database utilizing the path and determining whether the created database object is present in the database accessed utilizing the path, wherein if the created database object is present in the database accessed utilizing the path, the path is verified as a valid path to the database, and wherein if the created database object is not present in the database accessed utilizing the path, the path is determined to be an invalid path.

7. The method of claim 6, wherein the created database object is a temporary database object which is created during the method of verifying paths to the database, the method further comprising removing the temporary database object from the database upon completion of the process of verifying paths to the database.

8. The method of claim 7, further comprising:

closing the database upon verifying the paths to the database.

9. The method of claim 6, wherein determining whether the created database object is present in the database accessed utilizing the path comprises querying for the database object utilizing the path.

10. The method of claim 6, wherein the database object is an alias.

11. A software product comprising a set of computer instructions stored on a computer readable medium, the computer instructions executable by a computer processor to:

open a database utilizing a known path corresponding to the database;

create a database object in the database; and

for each path in a set of paths, verify the path by attempting to access the database utilizing the path and thereby determine whether the created database object is present in the database accessed utilizing the path, wherein if the created database object is present in the database accessed utilizing the path, the path is verified as a valid path to the database, and wherein if the created database object is not present in the database accessed utilizing the path, the path is determined to be an invalid path.

12. The software product of claim 11, wherein the created database object is a temporary database object which is created by the computer during the process of verifying paths to the database, the software product further comprising computer instructions executable by the computer processor to remove the temporary database object from the database upon completion of verifying the paths in the set of paths.

13. The software product of claim 12, further comprising computer instructions executable by the computer processor to:

close the database upon completion of verifying paths to the database.

14. The software product of claim 11, wherein determining whether the created database object is present in the database accessed utilizing the path comprises querying for the database object utilizing the path.

15. The software product of claim 11, wherein the database object is an alias.

16. A method for synchronizing databases in a set of databases, comprising:

for each database in the set of databases;

opening the database utilizing a known path corresponding to the database;

creating a database object in the database; and

for each of the paths in the set of paths, verifying the path by attempting to access the database utilizing the path and determining whether the created database object is present in the database accessed utilizing the path, wherein if the created database object is present in the database accessed utilizing the path, the path is verified as a valid path to the database, and wherein if the created database object is not present in the database accessed utilizing the path, the path is determined to be an invalid path.

17. The method of claim 16, wherein the created database object is a temporary database object which is created during the process of verifying paths to the database, the method further comprising removing the temporary database object from the database upon completion of the process of verifying paths to the database.

18. The method of claim 17, further comprising:

closing the each database upon completion of verifying paths to the database.

19. The method of claim 16, wherein determining whether the created database object is present in the database accessed utilizing the path comprises querying for the database object.

20. The method of claim 16, wherein the database object is an alias.