There was probably some change in the google API that needs a corresponding change in the mapviewer API.
File an SR/Bug if there isn't one already.
I am having this same problem. Why is it that the google maps pan/zoom (navigation) control does not show up in latest Mapviewer tutorial (reference Tutorial no B04), but it does in practice. There must be some work around being done in the tutorial, else why wouldn't the control show up?
I need this for a US State Agency trying to make a decision on whether or not to use MapViewer or restrict to ArcGIS Server only. Some direction would be greatly appreciated.
A couple of other issues worth noting as follows:
a) vector and tile layers can get out of sync from google tile layers when zooming in too far. Once out of sync, this is not corrected when zooming back out. Test this overlay vector roads on road maptype tile. Zoom in to zoom 17, then switch to satellite, then switch to shaded. After switching to shaded the mapviewer geometry and shaded goolge map become out of sync.
b) when zooming in to level 17 and larger, on the Satellite maptype, the Google imagery skews (perhaps changes into more of perspective geometry), thus making MapViewer vectors misalign. These are corrected once the user zooms back out to zoom 16 or smaller.
Note that the OP is probably talking about the v1 API, whereas you seem to be working with the V2 (html5) API. As far as we know only V1 has the dual zoom bar issue (and a fix will be coming soon in a patch).
Regarding the out of sync issue, do you have a test case or can reproduce it using our public tutorial page here (Oracle Mapviewer Tutorials)? You can directly modify the JS code there and click the Run button to activate the modified code. If you were able to reproduce the issues, please note the steps and code snippet here so we can do the same and diagnose if there is a real issue.
I have posted the entire html test script. It is based directly upon Mapviewer Demo Tutorials (B04 and B06) and v2. As you can see from below (reference to oraclemapsv2.js, OM object), I don't see how this could possibly be referencing v1. Please copy and paste into text file and give it a test (assuming port 7003 is not blocked) you should be able to directly verify points from the prior email points above.
I was able to fix this by making a change to the oraclemapsv2.js file. Search on navigationControl:false and replace it with zoomControl:false, panControl:false. After this, the google zoom and pan controls disappear.
Note this should be changed in the oraclemapsv2.js (and related files).