We are moving DB's from v11 to v17 and backing up each DB to NAS At first the backups using the drive letter wouldn't work, so we used the full name and it worked - now it's started to kick off again...
and throws the toys out with
Any ideas? I am aware that the NAS name is a typo, but it is correct nonetheless. Thanks |
They have come a long way with health care, but there is still no cure for stupid! The ones that were working also had the share name! Sigh...
Sorry :-( Glad you fixed it. FWIW, you can use EXECUTE IMMEDIATE with the ESCAPES OFF clause - that should make it easier to handle all those quadruple backslashes...
(16 Jan '17, 02:42)
Volker Barth
Also FWIW, I've found that (at least with SA17) I can use forward slashes, even under Windows, and thereby avoid all the 'escaping' (don't know if this is documented or not). This works well for me because I can then deploy to both Windows and Linux (where the forward slashes are required).
(16 Jan '17, 10:52)
Terry Wilkinson
Two useful bits of information :-) Thank you
(16 Jan '17, 10:54)
gchq
|
Is there a deliberately doubled "DB2" in the path? It does not appear in your code sample...
Mea Culpa - having one of 'those' days - only one DB2