“ipv6 equivalent” of 192.168.x.x (configuring a static ipv6 address)

I'm with Dave, I don't see the 0.0.0.0 that you're talking about.

You may, however, see a route to 0.0.0.0 in the route print command, which is the default gateway for your NIC. Your default gateway is where you go for access to any networks you don't know about.

Is this 0.0.0.0 address causing an actual problem?

Here are things I've noticed after working with IPv6 addresses:

1. Don't use "full" addresses. The :: abbreviation goes a long way.
2. Inside your organization you'll probably deal with a single prefix. This means you can all but ignore the first part of the address.
3. Unless you're using glass teletypes copy and paste exists. Use it.
4. As @TomTom points out, DNS exists. Use it.
5. When you start working with v6 addresses patterns will quickly emerge. You start to recognize things like organizational prefixes (HE, Cisco, etc), Teredo, ISATAP, and stateless autoconfiguration.

IPv6 address don't have to be complex. For example, this is the address of a large company's public web server:

2001:420:80:1::5

I'm assuming the "80" is a subnet reserved for web servers. Unlike IPv4 you could also use the subnet "443" for HTTPS-only servers.